Run output through `rustfilt` (or similar)

What is the feature you'd like to have?

I am trying to run some Rust-compiled binaries through BinaryNinja (via Dogbolt), but, while some of the "standard" symbols from the Rust library get unmangled, "user-defined" symbols don't (and also some standard ones as well!).

I hope this links works, but here's an example:

• https://dogbolt.org/?id=5ad47a7b-f10c-4777-a6f9-0c136fe2b401#BinaryNinja=863

You can see that some symbols are unmangled (e.g., std::io::stdio::_print::h9ced0fe1fdc237eb), but others (e.g., _RNvMs0_NtCsf8BuoUQGJw9_4core3fmtNtB5_9Arguments6new_v1Cs3D4dQeFb3sN_4rust) aren't.

Examples:

• _RNvMs0_NtCsf8BuoUQGJw9_4core3fmtNtB5_9Arguments6new_v1Cs3D4dQeFb3sN_4rust == <core::fmt::Arguments>::new_v1
• _RNvCs3D4dQeFb3sN_4rust5quack == rust::quack

Is your feature request related to a problem?

No; this is a "quality of life" improvement

Are any alternative solutions acceptable?

I can copy the output out of Dogbolt and run in through rustfilt myself.

Additional Information:

I originally reported this "idea" here:

• https://github.com/decompiler-explorer/decompiler-explorer/issues/157

I am happy to share binaries if it helps (but I believe that tool vendors on Dogbolt already have access to the binaries I submit).

Start by locating Binary Ninja's symbol demangling and output path, then compare its handling with the Rust symbols in the linked Dogbolt example. Done means Rust user-defined and standard symbols such as rust::quack and <core::fmt::Arguments>::new_v1 are displayed in readable form, with an appropriate validation example.