feat(coverage): enable regexp in test262

[Boshen]

@leaysgur This enables all test262 regexp tests, feel free to decide when's the right time to integrate.

It seems like we need to add some pointing spans on the diagnostics.

It's somewhat slow to run just c, so I always use just example parser for local development.

[graphite-app[bot]]

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

Add the label “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.

[codspeed-hq[bot]]

CodSpeed Performance Report

Merging #4242 will not alter performance

_{Comparing regexp-tests (33c80a7) with regexpp (bb54e3a)}

Summary

✅ 29 untouched benchmarks

[leaysgur]

feel free to decide when's the right time to integrate.

It looks like it will take a little longer, but understood. Thank you!

And I will catch up with the content of this PR as well. (BTW, I will be on an early summer vacation next week and will be unavailable. 🏖️ )

[leaysgur]

FYI:

• The previous CodSpeed result was one where the entire source code(!) was passed to the regexp parser, not the regular expression part
• I have not yet been started parser perf improvements

---

Benchmark results have been updated now.

I don't think current approach is not the best solution, but the CI is green. 😅

[IWANABETHATGUY]

FYI:

• The previous CodSpeed result was one where the entire source code(!) was passed to the regexp parser, not the regular expression part
• I have not yet been started parser perf improvements

Thanks for your explanation

[Boshen]

Continue in https://github.com/oxc-project/oxc/pull/4998