Skip to content

bpo-44283: Add jump table for match-cases of None, int, and str constants, as well as or-patterns of these. #26697

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

Closed
wants to merge 30 commits into from

Conversation

sweeneyde
Copy link
Member

@sweeneyde sweeneyde commented Jun 12, 2021

@sweeneyde sweeneyde marked this pull request as ready for review June 12, 2021 21:52
@sweeneyde sweeneyde requested review from markshannon, tiran and a team as code owners June 12, 2021 21:52
@brandtbucher brandtbucher self-requested a review June 17, 2021 16:55
@github-actions
Copy link

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Jul 18, 2021
Copy link
Contributor

@MaxwellDupre MaxwellDupre left a comment

Choose a reason for hiding this comment

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

Looks good on my machine, unfortunately cant check on windoz.

Copy link
Contributor

@MaxwellDupre MaxwellDupre left a comment

Choose a reason for hiding this comment

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

good

@github-actions github-actions bot removed the stale Stale PR or inactive for long period of time. label Aug 9, 2022
Copy link
Member

@brandtbucher brandtbucher left a comment

Choose a reason for hiding this comment

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

This was a cool experiment, but I think it's too big of a change right now (especially considering PEP 669 was just implemented, which doesn't support multi-way branches). Plus, most of the bytecode compiler and interpreter have been refactored since this change was implemented.

I suggest we close this. Thoughts, @sweeneyde? We could always refer to it if we decide this is worth doing in the future.

@sweeneyde
Copy link
Member Author

Sounds good to me. It is a little fishy to only work on literals anyway.

@sweeneyde sweeneyde closed this Jun 2, 2023
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.

6 participants