Miguel Ojeda

> Without stripping Yeah, I am just trying to look at it from the shoes of users working on proprietary software where it is common to strip it and clean/obfuscate/tweak...

(@bjorn3 To be clear, I wouldn't mind doing it by default and getting closer to GCC and Clang; I am just playing devil's advocate)

> Considering that this is annotated as [RFC], maybe you should open a PR to https://github.com/rust-lang/rfcs/ instead? Don't know how complex of a decision this is, so maybe a compiler...

> This is what you get when you run strings on rustc output that has debuginfo: Yeah, that is `DW_AT_producer`; however sometimes the debug info may not be available (this...

> * consistency with clang and gcc > * you have a use case: I need it for the linux kernel? To clarify a bit on those two you mention:...

> you started a FCP, but it is not obvious which option you are proposing should be selected: > > > The RFC part of this PR is about which...

HLSL when using DXC would also benefit from one of the solutions here.

Thanks a lot for this! > Be sure to select the library you want to use and then also use extern crate cratename; in your code Or compile with `--edition=2021`...

Yeah, I guessed it could be related to resource availability. It is still great to have it for the stable ones. Maybe later it could be introduced for a smaller...

We hit this with Linux kernel code like https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/include/linux/maple_tree.h#n75. I think providing a customizable prefix/suffix or moving the `typedef` inside a module with a customizable name would be the best.