(parser) Preserve exact floating point representation #412
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
perlun
added
enhancement
perlun
changed the title
perlun
force-pushed
the
feature/preserve-floating-point-string-values
branch
from
e9bcf15
to
9b4a133
Compare
perlun
changed the title
perlun
force-pushed
the
feature/preserve-floating-point-string-values
branch
from
9b4a133
to
56b4d59
Compare
The idea is to avoid losing the exact floating point representation as given by the user when constructing the parsed syntax tree. This will be useful in the compilation part (#409), where we want to avoid losing precision because of round-tripping to `double` and back to `string`.
perlun
force-pushed
the
feature/preserve-floating-point-string-values
branch
from
56b4d59
to
b3b0953
Compare
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.
The idea is to avoid losing the exact floating point representation as given by the user when constructing the parsed syntax tree. This will be useful in the compilation part (#409), where we want to avoid losing precision because of round-tripping to
doubleand back tostring.