Add context tracking for errors #18
Merged
Conversation
This file contains 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
|
Hang on, I'm adding a |
tertsdiepraam
approved these changes
Nov 11, 2024
src/error.rs
Outdated
| struct Information { | ||
| /// The primary error message. | ||
| /// | ||
| /// This is the innermost error to occur. |
There was a problem hiding this comment.
This is a bit strangely worded I think. There's only one error, so there's no innermost.
tertsdiepraam
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This enhances the
Errortype to store a "context stack", a way to tell where in a program the specific error occurred. For example, when parsing a zone file, context may be used to inform the user about the line number of a parse error. An extension trait forResulthas also been introduced that eliminates the need for.map_err()to add context.