feat: throw custom ExhaustiveError when no matched pattern#270
Merged
gvergnaud merged 1 commit intogvergnaud:mainfrom Jul 24, 2024
Merged
feat: throw custom ExhaustiveError when no matched pattern#270gvergnaud merged 1 commit intogvergnaud:mainfrom
ExhaustiveError when no matched pattern#270gvergnaud merged 1 commit intogvergnaud:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 adds/exports a custom
ExhaustiveErrorwhich will be thrown at runtime when amatchinput doesn't match any pattern and.exhaustive()has been specified. This gives better error handling capabilities, for example when trying to distinguish between an unmatched pattern error and an error thrown within a matched pattern's callback.Resolves #269