Result: map_err and deconstruct#11
Merged
Merged
Conversation
kinduff
approved these changes
Apr 22, 2026
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.
Surprised I went this long without
Result#map_err, I really need to make a full checklist of Result methods and see what else may be missing.Also
deconstructis pretty useful for pattern-matching on Result. Because Ruby has Exceptions, but exception-handling is optional, I find it fits the job that Errgonomic is doing to rescue certain (domain-applicable) exceptions, and return them with the Error side of a Result. Using deconstruct and Ruby pattern matching gives me a reasonable approximation of matching an enum in Rust.So far I think this is more helpful than it is uncanny valley. But this whole gem kind of flirts with that space.