TheVova

is there any update on this? im getting the same error for multiple builtins while linking rust libs to C code, ``` /home/vlad/arm-gcc/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: /home/vlad/arm-gcc/bin/../lib/gcc/arm-none-eabi/9.3.1/thumb/v7e-m+fp/hard/libgcc.a(_arm_addsubdf3.o): in function `__extendsfdf2': (.text+0x2c8): multiple definition...

Ok, so this breaks some tests atm because of the hidden assumption that Message implies Debug, which probably means it will break some user code that relies on this property....

im interested in this as well. removing Debug from `Message: Debug + Send + Sync` can the code a lot smaller for embedded use (where i dont want debug or...

cool. i'll fix this then. do we want it via codegen option in prost build so it can be set via `prost_build::Config` or as a feature in prost-derive?

I mainly meant the ergonomics of it for end users. if i wanna setup my codegen in my build.rs as is usually the case, i wanna be able to specify...

@almindor I dont think a linter would do it, was thinking this should maybe done at the language level itself. for example, looking at the source at /libstd/prelude/v1.rs, we find...

yeah, cargo no-no seemed cool, i did not know about it. As far as the corestd equivalence, from what i can gather from looking over the rust code, it is...

@jonas-schievink I dont know thats its unrelated to coherence... not internally, but from a user viewpoint, if the same operation behaved differently on the same type between std and core,...