2 ms·

I’m confused, wouldn’t RUST_BACKTRACE=1 effectively give you a stack trace?

• LegionMammal978 2y ago
  I think the scenario here is that a function unexpectedly returns an Err(...), but the program propagates it several frames upward before finally unwrapping it, which produces only a partial stack trace. This can be mitigated with error types like anyhow::Error which remember the originating stack trace, but such types aren't in common use in the library ecosystem.