fix floating point precision in floatyear_to_date #1747
Merged
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.
In this PR I fix a bug which was brought up by @Ruitangtang.
The problem was when calling
floatyear_to_date(1+1/12-1/12)
you expect to get(1, 1)
, but actually(0, 12)
was returned, due to a floating point precision issue. I now included a check if the given floatyear is inside machine precision to the next higher int, and if so us the next higher int instead.whats-new.rst