perf(parser): avoid checkpoint when parsing left curly in jsx

[ulrichstark]

This requires parse_jsx_expression_container and parse_jsx_spread_child not to expect LCurly because that's already bumped by the caller. Is that okay? Do I need to update the doc comments of both functions? Let's see if there are improvements in the benchmark...

Part of #11334

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11377 will not alter performance

_{Comparing ulrichstark:avoid-checkpoint-when-parsing-curly-in-jsx (b1a237b) with main (1cd8b9c)}

Summary

✅ 38 untouched benchmarks

[leaysgur]

FYI: I also tried to eliminate the rewind() for {expr and {...expr in #11314 (a12ff21), but there was no visible improvement. 😓

[Boshen]

Codspeed may not hit these code paths, let me double check.

[Boshen]

This is a really good change. I added a small change to avoid to at + bump check.

[graphite-app]

Merge activity

• May 30, 6:57 AM UTC: @ulrichstark we removed the merge queue label because we could not find a Graphite account associated with your GitHub profile.

You must have a Graphite account in order to use the merge queue. Create an account and try again using this link

[ulrichstark]

This is a really good change. I added a small change to avoid to at + bump check.

Thanks @Boshen! So I assume the doc comments of both functions are still fine and need no update.

Does it help when I create a Graphite account or can I just ignore those messages that I was removed from the merge queue?
Or is this only for core members?
Last time I tried creating a Graphite account and linking it to the oxc repo didn't work.