[issue46372] int/float specializations should mutate the LHS in-place when possible

Guido van Rossum added the comment: Since we decided to wait on the int operations while longobject.c is being refactored (https://github.com/faster-cpython/ideas/issues/245), can you clarify whether the speedup reported is from code where it is implemented only for floats, or is it from a

[issue46372] int/float specializations should mutate the LHS in-place when possible

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46372] int/float specializations should mutate the LHS in-place when possible

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46372] int/float specializations should mutate the LHS in-place when possible

Change by Raymond Hettinger : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46372] int/float specializations should mutate the LHS in-place when possible

Change by Brandt Bucher : -- keywords: +patch pull_requests: +28792 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30594 ___ Python tracker ___

[issue46372] int/float specializations should mutate the LHS in-place when possible

New submission from Brandt Bucher : The performance of our existing int and float specializations can be improved by mutating the LHS operand in-place when possible. This leads to significant speedups for several number-crunching benchmarks, and a solid 1% improvement overall: Slower (16):