perf(semantic): inline enter_kind for BindingRestElement

[camc314]

Ref #18098

[camc314]

• perf(semantic): inline enter_kind for FormalParameter #17400
• perf(semantic): inline enter_kind for BindingRestElement #17399 👈 (View in Graphite)
• perf(semantic): inline enter_kind for PrivateIdentifier #17398
• perf(semantic): inline enter_kind for ClassBody #17397
• perf(semantic): inline enter_kind for VariableDeclarator #17396
• perf(semantic): inline enter_kind for TSImportEqualsDeclaration #17394
• perf(semantic): inline enter_kind for ImportNamespaceSpecifier #17393
• perf(semantic): inline enter_kind for ImportDefaultSpecifier #17392
• perf(semantic): inline enter_kind for ImportSpecifier #17391
• 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.

[camc314]

Merge activity

• Dec 27, 8:55 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 27, 8:59 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Dec 27, 9:08 PM UTC: Merged by the Graphite merge queue.

[codspeed-hq]

CodSpeed Performance Report

Merging #17399 will not alter performance

_{Comparing c/12-27-perf_semantic_inline_enter_kind_for_bindingrestelement_ (9697948) with main (900d42d)¹}

Summary

✅ 42 untouched
⏩ 3 skipped²

Footnotes

1. No successful run was found on c/12-27-perf_semantic_inline_enter_kind_for_privateidentifier_ (a9ba2b2) during the generation of this report, so main (900d42d) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩