Support for tracing with `Std::panic::Location` (Feature Request)
Open
- Dominant language
- Rust
- Stars
- 5.5k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
Hello there
It's sometime useful to simply trace the location of an error's origin, through nested callers and micro managed errors.
Compared to already existing `Backtrace`, it might be more concise, and thanks to `std::panic::Location` and `#[track_caller]` being stabilized it wouldn't need nightly.
Thanks for the great crate
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.