Conversation
…ocument derive Allows specifying a custom error type for the generated ParseDocument impl. The custom error type is used instead of ParseError for `type Error`. The custom type must implement `From<ParseError>` for `?` to work. This enables: - Combining multiple error sources with enum error types - Adding custom validation errors from nested ParseDocument impls - Using domain-specific error types throughout the parsing chain
ryo33
force-pushed
the
claude/custom-error-derive-1hJgf
branch
from
0748675 to
ff58fab
Compare
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
2 participants
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.
Allows specifying a custom error type for the generated ParseDocument impl.
The custom error type is used instead of ParseError for
type Error.The custom type must implement
From<ParseError>for?to work.This enables: