Arkadiusz Piekarz

I feel like your issue is similar to mine for an improvement in The Rust Book - https://github.com/rust-lang/book/issues/1940. It got a few voices of support, but unfortunately was closed. It...

@BenjaminRi What you described is a unit test, while the questions in this thread were about integration tests. Note that the code under`cfg(test)` is not compiled in the latter.

@EpiFouloux That sounds like unit tests, not integration ones, because in the latter `cfg(tests)` is not compiled. Can you try what I described in https://github.com/rust-lang/book/issues/1940?

@EpiFouloux For clarity I changed them into "my_library" - it's just the name of your project you are working on, structured as a library. That library can then be used...

I would also like to see this change implemented. Currently enums with a few words in their names get hard to read generated constants for their count. Users are already...

@thanm I would like to use it together with [Boost.Stacktrace](http://www.boost.org/doc/libs/1_66_0/doc/html/stacktrace.html), a library for printing stack traces on demand or at application crash. Libbacktrace is [one of many backends](http://www.boost.org/doc/libs/1_66_0/doc/html/stacktrace/configuration_and_build.html) that Boost.Stacktrace...

Will the proposed change fix the following problem when `resolver = "2"` is present in `Cargo.toml`? ``` $ cargo outdated error: failed to parse manifest at `my-project/Cargo.toml` Caused by: feature...

For what it's worth, Boost already provides a portable demangling utility in Boost.Core - https://www.boost.org/doc/libs/1_75_0/libs/core/doc/html/core/demangle.html

One year has passed since opening this issue, are we closer to getting Windows support?

It looks like it's available now - https://bintray.com/bincrafters/public-conan/boost_callable_traits%3Abincrafters