This repository was archived by the owner on Apr 2, 2026. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 210
Add map_err_with()
#951
Merged
+101
−4
Merged
Add map_err_with()
#951
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I think this change is a positive, I am a bit worried about users relying on things like
MapExtra::slice,MapExtra::span, etc. Chumsky deliberately permits parsers to leave the input in an unspecified state after an error occurs and backtracking begins (it's up to calling parsers to explicitly rewind the input if they need recovery). As such, I think we should explicitly document that these functions may not produce the output a user might expect.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, while implementing this I was wondering what to provide to the closure. So I think you're saying that all of
MapExtrais too much because some of it doesn't make much sense in case of an error?Just
span(map_error_with_stategets this at the moment though maybe computed differently),stateandcontextthen? Should it be a new struct or just passed individually to the closure? If it's the latter, this new function would be basically like the existingmap_error_with_statebut with one additional argument.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm honestly not sure! For now, I think the easiest approach (and most consistent with the rest of the crate) is to stick with
MapExtra, but document that the output ofMapExtra::spanandMapExtra::sliceare unspecified. This certainly warrants further thought, but I don't think it should block this PR. I'll merge when the change is made to the docs, thanks.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a warning. Let me know if I should change the wording.
Should I also add a deprecation note for
map_err_with_state()?