We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After looking at the fun uses of await and delete that we get after #883, I found that civet accepts this kind of input
await
delete
x.filter not.condition x.forEach delete.old ↓↓↓ x.filter(($) => !$.condition); x.forEach(($1) => delete$1.old);
In my opinion either this should be invalid syntax or there should be a space after delete
This trick doesn't work with await:
x.map await.json() ^ ParseError
The text was updated successfully, but these errors were encountered:
Stricter unary operators (before &)
9466a35
Fixes #885
Thanks for spotting this so quickly! Should be fixed by #886.
Sorry, something went wrong.
edemaine
Successfully merging a pull request may close this issue.
After looking at the fun uses of
await
anddelete
that we get after #883, I found that civet accepts this kind of inputIn my opinion either this should be invalid syntax or there should be a space after delete
This trick doesn't work with
await
:The text was updated successfully, but these errors were encountered: