RUSTSEC-2020-0036: failure is officially deprecated/unmaintained about symbolic HOT 4 CLOSED

Thanks! We are looking to remove failure in favor of std::error::Error soon.

In the past, the only blocker for us has been missing stabilization of Error::backtrace, which we rely on heavily in our production services. However, we've recently come to the conclusion that libraries like symbolic should not capture backtraces on their own, so I believe that we can now start to replace failure.

from symbolic.

I’m starting to work on this, first in symbolicator, which has no semver requirements and can therefore internally break whatever it wants. After gaining some experience in this, we will try to tackle symbolic. The challenge here is to do it without breaking the API, for example by doing it behind a feature flag.

from symbolic.

failure was removed some time ago, and we don’t even have it in transitive dependencies anymore.

from symbolic.

Any update on this?

from symbolic.