@mathias Are regexes intentionally not verified in lazy parsed func bodies?
```
function f(){ /)/ }
() => /)/
[{l(){ /)/ }}]
```
Does throw for `/)/` in toplevel or inside toplevel expression or in iife...
-
-
oh I guess I'll wait for its 10 year anniversary before reporting it again :D
-
Oh no! :P To be fair,
@verwaest recently fixed the non-RegExp cases (late → early errors) as part of his work on the parser: https://v8.dev/blog/preparser#teaching-the-preparser-about-variables … RegExp is a different beast, though. cc@hashseed@schuay@peterwmwong - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.