Is there any option to have Nim's C backend generate more readable/descriptive mangled function names? Sometimes I have to look at those names, when using native profiling/debugging tools, and they can be very ambiguous. For example, `write__UlykqHUJzrYfskoCKJB7AQ` is obviously a function named `write` ... but which one? Sometimes it's clear from the stack backtrace, but not always, especially when the stack dives deep into library code.
I'm assuming the gibberish is a base64 digest of the function signature and maybe the compiler settings too. It'd be nice if, for these purposes, I could temporarily switch to a more C++ like mangling that makes the parameter types [sort of] readable. (I've checked the compiler documentation but didn't find anything.)
