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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix millisecond fraction being handled with wrong scale #65
fix millisecond fraction being handled with wrong scale #65
Changes from 2 commits
6a79b44
a624253
617c962
26dd249
bca5c31
6579bdb
e013642
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for fixing my issue (#61). But I wonder about this strategy here, reusing an integer parsing function for a fractional part:
As an example, consider an input like
1711445175.+07186
which should probably be invalid, not parsed as if the+
were a zero.Perhaps the
i = int_parse_bytes(fract)
function could be copied as a(i, magnitude) = fract_parse_bytes(fract)
function, where themagnitude
would be safer than relying onfract.len()
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say if we use a
max_digits
pattern above, it seems intuitive to then error if the number of decimal digits violates that standard.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a behavioural change but I think correct given the spirit of the config.