result and option #2
Merged
Conversation
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
schneems
reviewed
Mar 5, 2025
schneems
reviewed
Mar 5, 2025
schneems
reviewed
Mar 5, 2025
schneems
reviewed
Mar 5, 2025
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.
Okay fine, let's do this. Add yard-doctest and go to town making a take on Result and Option that feels like Ruby.
The first take was a lot smaller and more opinionated. The kind of thing I could easily and uncontroversially drop into a Rails project. This next take is… unapologetic in bringing my Rust reflexes into Ruby. But may not be something I want to use in Rails.
More thought will be required about how I want to use this, but it sure was fun to write, especially after finding yard-doctest.