Eric Huss

The sources are at: * lldb: https://github.com/llvm/llvm-project/blob/main/llvm/lib/Demangle/RustDemangle.cpp * gdb: https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=libiberty/rust-demangle.c;h=8dfeeac2a4fe44a82da54a2e4d9327e9b5b1c257;hb=HEAD if that's what you are asking for. This is for v0 mangling, which is currently (https://github.com/rust-lang/rust/issues/60705) still not the default...

There is now a dedicated chapter for this at https://rustc-dev-guide.rust-lang.org/tests/ci.html. However, I didn't add links to it from the other places.

The Cargo team discussed this RFC, and we think the following may be a viable path forward: 1. Generate a warning if a dependency version has a pre-release version without...

Yea, that's another drawback where the switch is lossy. A few thoughts on that: * If using workspace inheritance, there should only be one place to fix these. * Presumably...

Closing as I believe this is resolved by #10907.

A proposal to stabilize this has been posted at #11224.

Sparse registries are now stabilized and will be available in Rust 1.68, which will be released on 2023-03-09. I'm going to close this tracking issue as I think it has...

I'm still a little fuzzy on the exact use cases for this. Can you show an example of when this would be used? The original motivation wasn't a very strong...

Thanks @Nemo157 for picking this back up. @weihanglo I recommend adding `resolver = "1"` to the rust-lang/rust workspace when you do the next update so that warnings don't start getting...

Reopening since in #11960 we are planning to mark -C as unstable for now.