Fix error on parsing a floating point value which ends with a dot #382
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.
As reported in the issue #380, the current parser emits an error on parsing a floating point value which ends with a dot.
That is because, while scanning a parsed scalar, the parser mistakenly assumes decimals after a dot.
However, the spec explicitly allows omitting decimals after a dot here as the regular expression for the float tag.
So, this PR has fixed implementation to follow the spec, and the updated parser now correctly parse such floating point values.
To validate the changes, some relevant test cases have also been added to the test suite.
Pull Request Checklist
Read the CONTRIBUTING.md file for detailed information.
Please don't
#ifdef
s or other means.