-
-
Notifications
You must be signed in to change notification settings - Fork 188
[Feature] std::panic::Location support #291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
update with upstream
This is a solid change. I've started using it in a project of mine and it's working great. |
+1 |
Anything blocking the merge of this? It would be a great feature to have! |
Working for this one to be merged too, any plans ? 👀 |
I'm gonna resolve the merge conflicts at some point but this should be working on the latest version soon™ I have like, negative free time rn. |
this is up-to-date and ready. all tests completed successfully @dtolnay can this merge? |
Implements automatic call site location capture for error types with &'static Location<'static> fields. Location fields are automatically populated when From trait conversions occur, enabling precise error location tracking without manual instrumentation. Features: - Auto-detection of Location<'static> fields in structs and enum variants - Optional #[location] attribute for explicit field marking - Automatic From impl generation with #[track_caller] - Support for both named and tuple enum variants - Location populated via Location::caller() during From conversion - No #[from] attribute required on location fields Based on dtolnay#291 by @onlycs (Angad Tendulkar) Closes dtolnay#142 - Support for tracing with std::panic::Location Co-authored-by: Angad Tendulkar <[email protected]>
- Rebrand from thiserror to wherror across all packages - Add comprehensive README documentation for location feature - Update all imports and references throughout codebase - Add location support implementation with automatic call site capture - Include proper attribution to original thiserror and PR dtolnay#291 authors
This would be amazing to see merged <3 |
closes #142