-
Notifications
You must be signed in to change notification settings - Fork 64
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
Optimize error handling #405
Comments
yeah the stack trace looks nice. i'd be up for using it |
demo code, i've written a simple demo, mostly based on greptimedb's impl, since they haven't published the error handling crate yet, it shall be much more convenient to take a glance at their ideas of virtual user stack , the blog is already pasted above |
Nice! Planning to make a crate for this? |
Nnope, the idea belongs to greptime db, i just wondered how easily can we adopt it in our project. Is this way of error handling better from your point of view? After which i shall start the refactor in this project. |
Ok makes sense. Yeah I like it, seems clean way to track error stack and easier to report the where the error originates. |
Motivations: greptimedb has done an excellent job in error handling, see: https://greptime.com/blogs/2024-05-07-error-rust
Shall we adopt some ideas from it?
The text was updated successfully, but these errors were encountered: