Use `#[track_caller]` to provide info on where the error was created
laralove143 opened this issue · 1 comments
laralove143 commented
Sometimes, backtrace is overkill or it doesn't work well enough (especially in async). This proposal allow a more concise, performant and reliable (although limited) method to provide information about where in the source the error first occurred.
It should be behind a feature flag, like backtrace (though not mutually exclusive). When the feature is enabled, the location should be added to the error's Display, Debug or alternate debug implementation.