perf(transformer/jsx): no string comparisons generating pragma expression

[overlookmotel]

#7553 introduced support for some unusual JSX pragmas e.g. this.foo and import.meta.foo. We want to support these to pass tests, but they're very unlikely to be used in practice.

Identify these strange patterns when parsing the pragma (which happens only once per file), and encode them as an enum. The removes expensive string comparisons from Pragma::create_expression (which is called for every JSX element), and keeps the path for common cases fast.

[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.

[overlookmotel]

• perf(transformer/jsx): no string comparisons generating pragma expression #7620 👈 (View in Graphite)
• refactor(transformer/jsx): Pragma::parse take a &str #7619
• test(transformer/jsx): move tests setup into a macro #7618
• main

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

[codspeed-hq]

CodSpeed Performance Report

Merging #7620 will not alter performance

_{Comparing 12-03-perf_transformer_jsx_no_string_comparisons_generating_pragma_expression (3b1e63e) with main (fcc2546)}

Summary

✅ 29 untouched benchmarks

[Boshen]

Merge activity

• Dec 3, 9:02 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 3, 9:02 PM EST: A user added this pull request to the Graphite merge queue.
• Dec 3, 9:59 PM EST: A user merged this pull request with the Graphite merge queue.