python / python/cpython

Add jump table for certain safe match-case statements

Open
#88,449 20 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

3.12 interpreter-core performance
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 44283
Nosy @rhettinger, @markshannon, @serhiy-storchaka, @corona10, @brandtbucher, @sweeneyde, @AndersMunch, @Fidget-Spinner, @Kshitiz-Arya
PRs
  • python/cpython#26697
  • Files
  • matchperf.py
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = None
    created_at = <Date 2021-06-01.21:58:12.002>
    labels = ['interpreter-core', '3.11', 'performance']
    title = 'Add jump table for certain safe match-case statements'
    updated_at = <Date 2021-06-14.17:02:35.709>
    user = 'https://github.com/sweeneyde'
    

    bugs.python.org fields:

    activity = <Date 2021-06-14.17:02:35.709>
    actor = 'brandtbucher'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2021-06-01.21:58:12.002>
    creator = 'Dennis Sweeney'
    dependencies = []
    files = ['50106']
    hgrepos = []
    issue_num = 44283
    keywords = ['patch']
    message_count = 20.0
    messages = ['394874', '394878', '394882', '394884', '394887', '394889', '394891', '394892', '394975', '394977', '395019', '395069', '395265', '395278', '395717', '395732', '395738', '395797', '395809', '395813']
    nosy_count = 9.0
    nosy_names = ['rhettinger', 'Mark.Shannon', 'serhiy.storchaka', 'corona10', 'brandtbucher', 'Dennis Sweeney', 'AndersMunch', 'kj', 'Kshitiz17']
    pr_nums = ['26697']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'performance'
    url = 'https://bugs.python.org/issue44283'
    versions = ['Python 3.11']
    

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    Research direction

    Start by reviewing the existing python/cpython#26697 pull request and the referenced matchperf.py benchmark. Determine which safe match-case statements are in scope and how the jump-table change should be evaluated; the work is done when the targeted cases use the intended optimization and the relevant performance behavior is verified.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    python
    Domain
    compilers, performance
    Issue type
    Feature
    Difficulty
    5/5
    Estimated time
    Over a week
    Activity status
    Stale
    Clarity
    Needs clarification
    Newbie friendliness
    20/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.