Parsing incorrect if number text has thousands separator(s)#110
Closed
nietras wants to merge 1 commit intoCarlVerret:masterfrom
Closed
Parsing incorrect if number text has thousands separator(s)#110nietras wants to merge 1 commit intoCarlVerret:masterfrom
nietras wants to merge 1 commit intoCarlVerret:masterfrom
Conversation
Contributor
Author
|
another issue is that whitespace characters are not counted towards characters consumed, not sure if reason for not doing this?
|
Collaborator
|
Thanks. I’ll have a look. I do not expect thousand separators to work: I don’t think that it was ever was advertised. |
Contributor
Author
No it isn't, however I made the mistake of thinking this meant parsing would fail/return false for case with such characters in text, I have changed to check consumed chars and if text contains thousand separators. |
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
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.
I was not aware of this, but it appears csFastFloat does not parse numbers correctly if text has thousands separators? Is that not handled in
fast_float? The test fails for"1,234,567.89"with: