Skip to content
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

GH-106529: Define POP_JUMP_IF_NONE in terms of POP_JUMP_IF_TRUE #106599

Merged
merged 3 commits into from
Jul 11, 2023

Conversation

markshannon
Copy link
Member

@markshannon markshannon commented Jul 10, 2023

Likewise POP_JUMP_IF_NOT_NONE in terms of POP_JUMP_IF_FALSE.

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, this should work with gh-106551 once that's ready.

@gvanrossum
Copy link
Member

gvanrossum commented Jul 10, 2023

FWIW, I tried to come up with a test case for this, and finally realized these two opcodes are only emitted by compile.c for except*...

@gvanrossum
Copy link
Member

I pushed merge (since the conflict was my fault) but I'll leave it to you to land.

@markshannon markshannon merged commit c0c041a into python:main Jul 11, 2023
15 checks passed
@markshannon markshannon deleted the micro-op-jump-if-none branch August 6, 2024 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants