-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Support for nullish coalescing operator (??) #559
Comments
It's worth noting that this proposal is at stage 4, so it's stable and will end up in the language, possibly in the next spec. |
I patched in "this is not an error" like this:
Is there a similarly easy advice to add support for the ?? as for private fields (#537)? https://github.com/tc39/proposal-nullish-coalescing Short form:
|
Would somebody like to try implementing the proper support for it? |
Merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is related to, but not the same as, the optional chaining feature implemented by #533/#506. See:
As of now, an expression like
x ?? "default"
appears as a linter error from the second?
onward - it'd be great to have linter support for this new language feature.I wanted to try and open a PR for this feature myself, but after reading the code, I felt pretty unqualified in the elisp and syntax-parsing knowledge department. I'm still going to try to hack at it this weekend, but I may not be able to produce anything that works by myself 😬
The text was updated successfully, but these errors were encountered: