@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...
-
Show this thread
-
I should probably clarify that I'm asking for v8. This was at least the case for node 12 and chrome devtools console.
2 replies 0 retweets 1 likeShow this thread -
Replying to @kuvos
They’re supposed to be early errors indeed, but they currently aren’t in V8: https://bugs.chromium.org/p/v8/issues/detail?id=896 …
1 reply 0 retweets 1 like -
Replying to @mathias
oh I guess I'll wait for its 10 year anniversary before reporting it again :D
1 reply 0 retweets 1 like -
Replying to @kuvos
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@peterwmwong2 replies 0 retweets 0 likes -
I fixed all variable conflicts early errors, I didn't look at regexp scanning. (Although verwaest@ is also a Toon, please refer to tverwaes@ :-))
1 reply 0 retweets 1 like
Most subtly confusing GitHub/Twitter/Chromium username combo ever
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.