@andruud wrote in #6312 (comment)
The reason Chromium appears to evaluate
not fn()to false in the demo is becausenot fn()is actually invalid grammar. (<any-value>, requires one or more tokens).
Since this is about forwards-compatible parsing and evaluation, it seems to me it would make more sense if <any-value> were optional so that empty functional notations would be syntactically valid.
You can’t perform that action at this time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3