Skip to content

Track error conversion locations using #[track_caller] #155

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

Open
kesyog opened this issue Mar 30, 2022 · 1 comment
Open

Track error conversion locations using #[track_caller] #155

kesyog opened this issue Mar 30, 2022 · 1 comment

Comments

@kesyog
Copy link
Contributor

kesyog commented Mar 30, 2022

#123 added a crate-wide Error type and some helper macros to add logs gated by the log feature. One could use the new macros everywhere to provide additional context to errors for debugging. But it might be possible to use #[track_caller] and core::panic::Location to automatically track and log where errors originate and where they get converted to other error types, eliminating a bunch of tedious work. Investigate this and implement if possible.

References

@kesyog
Copy link
Contributor Author

kesyog commented Mar 30, 2022

I'll take this on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant