Eduard-Mihai Burtescu

This would be the fourth non-Rust demangler for Rust (libiberty, IllumOS, LLVM off the top of my head). I would suggest reusing [the libiberty one](https://github.com/gcc-mirror/gcc/blob/b8944f0438a183a0245ffe17aeaeaf3a1a00069c/libiberty/rust-demangle.c) (that I wrote - let...

> If the Rust demangler in libiberty were in its own repo and can be compiled to a simple command that just demangles a mangled symbol, it would have been...

(Sorry for not getting back to this in the past month, other things kept coming up etc.) So I just took a look over the emails for my libiberty contributions,...

Finally got around to setting up that repo I kept promising: [`rust-demangle.c`](https://github.com/LykenSol/rust-demangle.c). However, I ran out of time this weekend to actually implement anything new, and only got around to...

Oof, C++ compat (0e88fd047e01a32aba268d39841c3daf3c38baf7) definitely is something I should've handled (thought of it but then forgot). But I don't think it's going to work within the `if (name.starts_with("_Z")) {` check...

> Is there any regression from the C++ users's point of view if we attempt to demangle a string as a Rust mangled name before as a C++ mangled name?...

@rustbot second (I've been wanting to do some things in this area, and was expecting to remain WF-unsound for a while w/o a `Tuple` trait)

@rustbot second (accidentally reinvented parts of this design the other day)

@rustbot second (hope I'm not overstepping here - this has been one of my major gripes with MIR over the years)

@gnzlbg You can have a `const` of uncloneable type e.g. `Option` (it would just not have uncopyable *leaf* data, i.e. it would need to be `None`). But also, I don't...