GeezerVison is showing github.com — Minor refactoring of Object/abstract.c (UNARY_FUNC macro and more cases for BINARY_FUNC) by skirpichev · Pull Request #112145 · python/cpython
Conversation
skirpichev
commented
Nov 16, 2023
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
- Use BINARY_FUNC macro for some remaining ops
- Add UNARY_FUNC macro to define unary PyNumber_* functions
// from #111996
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
gst reacted with thumbs up emoji
(from python#111996)
* PyNumber_AsSsize_t: remove inaccessible code (PyLong_AsSsize_t raises OverflowError)
* Drop checks for broken float subclasses (like for PyNumber_Long in 31a6554)
* Ternary ops (currently only pow/ipow) don't use __r*__ dunders, thus
removal of testing last slot in ternary_op()
* Use BINARY_FUNC macro for some remaining ops
* Add UNARY_FUNC macro to define unary PyNumber_* functions
|
CC @serhiy-storchaka, this was abstract.c diff from the referenced pr. I hope this can skip issue and news entry...
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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 deserves 4 or 5 separate issues.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
It deserves 4 or 5 separate issues.
Huh. Is it worth or code should be kept intact?
Reusing old or adding new macros is a secondary issue. All others related to a dead code (for different reasons). So, having something in common.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Dec 3, 2023
skirpichev
changed the title
Minor refactoring of Object/abstract.c
Minor refactoring of Object/abstract.c (UNARY_FUNC macro and more cases for BINARY_FUNC)
Dec 3, 2023
skirpichev
commented
Dec 3, 2023
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
@serhiy-storchaka, now this has only UNARY/BINARY_FUNC stuff. Probably this not worth an issue and can skip news.
Description was updated.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
aisk
pushed a commit
to aisk/cpython
that referenced
this pull request
Feb 11, 2024
…es for BINARY_FUNC) (pythonGH-112145)
* Use BINARY_FUNC macro for some remaining ops
* Add UNARY_FUNC macro to define unary PyNumber_* functions
Glyphack
pushed a commit
to Glyphack/cpython
that referenced
this pull request
Sep 2, 2024
…es for BINARY_FUNC) (pythonGH-112145)
* Use BINARY_FUNC macro for some remaining ops
* Add UNARY_FUNC macro to define unary PyNumber_* functions
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|