perf(parser): reorder parse_statement match conditions

[Boshen]

For performance reasons, match orders are:

1. plain if check
2. check current token
3. peek token

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[Boshen]

• perf(parser): reorder parse_statement match conditions #7645 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Performance Report

Merging #7645 will not alter performance

_{Comparing 12-04-perf_parser_reorder_parse_statement_match_conditions (d503a84) with main (e923e4e)}

Summary

✅ 29 untouched benchmarks

[Boshen]

Merge activity

• Dec 4, 7:31 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 4, 7:31 AM EST: A user added this pull request to the Graphite merge queue.
• Dec 4, 7:36 AM EST: A user merged this pull request with the Graphite merge queue.