Improved error handling #29
Merged
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
1. `Symbol#match` and `String#match` surprisingly doesn't have the same return type 2. Raise a better error on an unknown token
|
Sorry for the slow response. Thank you for the fix. This should be part of the 1.3 release shortly. |
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.
Consider the following expression:
This expression contains an invalid json-value, and this will raise the unhelpful error
unexpected token 0. The reason for the zero is thatSymbol#matchsurprisingly returns a fixnum, unlikeString#match. Still,unexpected token unknownwould not be much better, therefore unknown tokens raise a separate error, in this caseunknown token "foo".(Note that this particular expression is accepted by other implementations, but I don't think it should be according to the specification.)