perf(parser): remove a bound check in match_keyword

[Boshen]

This is on a really cold path, so no expected performance improvement.

[Boshen]

• perf(parser): remove a bound check in match_keyword #12778 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

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

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #12778 will not alter performance

_{Comparing 08-03-perf_parser_remove_a_bound_check_in_match_keyword_ (00bdfc0) with main (09ae2a9)¹}

Summary

✅ 34 untouched benchmarks

Footnotes

1. No successful run was found on main (00bdfc0) during the generation of this report, so 09ae2a9 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[Boshen]

Merge activity

• Aug 3, 10:55 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Aug 3, 11:37 AM UTC: Boshen added this pull request to the Graphite merge queue.
• Aug 3, 11:43 AM UTC: Merged by the Graphite merge queue.