-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
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
Nullish coalescing operator ??
#203
Comments
Hmm. Adding it as a @hzoo @loganfsmyth @danez What do you think? |
|
In the proposed specification |
@codehag The organisation and names of the grammar productions in the spec should not affect our designs here. Also, estree cannot make backward incompatible changes such as the one you suggest. |
ok, thanks for the context |
Thanks for the replies here. We're implementing this in SpiderMonkey with |
👍 Terser will follow suit. |
This issue is fixed by #211. |
@JLHwung Right, thanks. |
Stage 3 proposal
Spec repo: https://github.com/tc39/proposal-nullish-coalescing
(Related to #146 optional chaining, but an independent proposal.) We just implemented
??
in SpiderMonkey. It's a short-circuiting binary operator, more like||
than anything else, but calling it aLogicalExpression
is a stretch.The text was updated successfully, but these errors were encountered: