Closed
Conversation
This lets you replace the input field in a `ParseError`, e.g. to transform a `ParseError<&str, E>` into a `ParseError<String, E>`.
4cb4a4a to
c9c92cb
Compare
Pull Request Test Coverage Report for Build 11334127920Details
💛 - Coveralls |
Collaborator
|
We ask that new features start as issues to explore the underlying use case and requirements and then discuss how we want to solve the problem. We then move onto PRs to discuss the implementation. |
Contributor
Author
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
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 lets you replace the input field in a
ParseError, e.g. to transform aParseError<&str, E>into aParseError<String, E>. I'd like this so that I can have an ownedParseErrortype, but only if a top-level parse fails.