demonstrate "refactor error away" pattern #32
Conversation
This file contains 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
One of the most powerful error-handling techniques is eliminating the possibility of a certain category of error. For example, word-counting doesn't *fundamentally* depend on IO, and, with some work, we can actually remove all error-handling from the library.
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.
One of the most powerful error-handling techniques is eliminating the
possibility of a certain category of error. For example, word-counting
doesn't fundamentally depend on IO, and, with some work, we can
actually remove all error-handling from the library.
Don't expect this to be merge, just want to steal your awesome example to demonstarte the pattern! Thanks for the article and for the accompanying code!