| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
What is the performance impact on math.floor(1.0) and math.ceil(1.0)? Faster, slower, no significant impact?
Sorry, something went wrong.
|
This PR needs tests. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for this PR. Some changes are needed:
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @mdickinson: please review the changes made to this pull request. |
Sorry, something went wrong.
|
I submitted benchmarks to bpo |
Sorry, something went wrong.
There was a problem hiding this comment.
Changes LGTM; thank you! The performance is still a concern, but if some form of #16991 gets merged then that wouldn't be so much of an issue.
@serhiy-storchaka @vstinner Does the current state of the PR seem okay to you?
Sorry, something went wrong.
|
#16991 will solve the performance issue for exact floats, but not for subclasses. |
Sorry, something went wrong.
I don't think there's too much reason to care about fine-tuning of performance for float subclasses. The most common subclass is NumPy's float64, and if you're using NumPy you're likely using NumPy's floor instead of math.floor anyway. |
Sorry, something went wrong.
|
me:
I checked the current implementation of math.floor(): there is a fast-path for exact type float which does something like PyLong_FromDouble(floor(PyFloat_AS_DOUBLE(number))). I'm fine with calling the __floor__() method for subclasses. That's the purpose of subclasses: being able to override some methods. That's part of the Python semantics. |
Sorry, something went wrong.
Oh, that's @serhiy-storchaka 's PR #16991 which has just been merged. I didn't notice ;-) |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. There is no performance overhead on math.floor() and math.ceil() for exact float.
I'm fine with having a small overhead for float subclasses. I didn't measure the overhead, I expect it to be really small or even not significant.
Sorry, something went wrong.
|
@mdickinson @serhiy-storchaka: I'm not sure that you agree, so I didn't merge the PR. I approve the PR, so I'm fine with merging it. What about you? |
Sorry, something went wrong.
|
@mdickinson @serhiy-storchaka: I plan to merge this PR next Friday (December 21) if no one replies. @isidentical: Please ping me next Friday if I forget to merge your PR. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
https://bugs.python.org/issue38629