[Experiment] Integrate error-stack for better error and stacktrace reporting - #2
Closed
mzruya wants to merge 2 commits into
Closed
[Experiment] Integrate error-stack for better error and stacktrace reporting#2mzruya wants to merge 2 commits into
mzruya wants to merge 2 commits into
Conversation
mzruya
force-pushed
the
mz.error_improvments
branch
from
April 1, 2023 18:19
5827094 to
6084929
Compare
mzruya
changed the title
Contributor
Author
|
Closing in favor of #3 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
error-stack is a fairly recent Rust error reporting library meant to build richer and more concise error reports. Using it adds boilerplate and forces explicit error types across all fallible methods. The result is a much more concise and clear terminal output when something goes wrong.
For example:
Or:
I'm not yet sure the boilerplate is worth it, color-eyre, an older error reporting library might be a better fit. It would allow for good enough error traces, without being forced to define error types for every layer in the stack. (Here's an alternative using color-eyre).