You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you place a paranthesised function on a line after a non paranthesised function, you get a compiler error that claims that your code is not JavaScript and that an identifier was expected.
This is a bug (in esrap — we're not wrapping a FunctionExpression in parens if it's a direct child of an ExpressionStatement) — but I'm very curious about how you ended up here in the first place. That code doesn't... do anything?
I'm very curious about how you ended up here in the first place. That code doesn't... do anything?
I was looking for other bugs and stumbled upon this one. Some of the other possible bugs I was testing were to see if the compiler would insert unnecessary $.gets in closures, and if the state symbol would appear in $state proxies.
Describe the bug
If you place a paranthesised function on a line after a non paranthesised function, you get a compiler error that claims that your code is not JavaScript and that an identifier was expected.
Reproduction
Reproduction
Logs
No response
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: