Josh Triplett

This looks great, thank you. I'd love to have this available, and I'd be happy to adapt the Rust package to use a version with this change.

This seems entirely reasonable to me. One thing the RFC should discuss, though: will all platforms that use a given target have the same *interpretation* of the type? Is the...

@reitermarkus If the socketaddr types aren't identical across platforms, I don't think we want them in core.

This seems reasonable to me, including the step of (eventually) making this default to enabled in release builds. That'll allow people to turn it on in debug if they need...

@kornelski > Would it be possible to separate trimming of paths inside executables from trimming of paths in external debug files? That seems like a really good plan. We could...

Something that came up in today's @rust-lang/cargo meeting: we should set a variable `CARGO_TRIM_PATH` or similar for `build.rs` scripts.

I like the concept of this. I feel that this should be an extension to artifact dependencies, rather than just a related feature as this RFC presents it. In particular,...

Following up on this: I went through previous feedback, resolved a couple of threads, and commented in others. I *think* this is now ready to update to incorporate the remaining...

> Lets say you want to build application NN with zlib-ng-native, and its dependency-tree has a ton of libraries, and one or more tightly system-integrated libraries depends on zlib-nb-compat. Been...

Using the symbol prefix feature would make those libraries incompatible with C code that's expecting either the zlib API or the native zlib-ng API. And in any case, the symbol...