tc39 proposal-nullish-coalescing issues - Githubissues

tc39 / proposal-nullish-coalescing

Nullish coalescing proposal x ?? y

https://tc39.github.io/proposal-nullish-coalescing/

1.23k stars 23 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Change operator to ||| and reserve ?? for optional chaining

#17 dfahlander closed 1 year ago
16
this proposal is too confusing for users to use correctly. nodejs' util.isNullOrUndefined does the job already.

#16 kaizhu256 closed 5 years ago
1
Precedence

#15 littledan closed 4 years ago
26
why modify the language when a trivial helper function returnNotNullishOrDefault() can suffice?

#14 kaizhu256 closed 6 years ago
12
Clarify what happens for 'a ?? b' when 'a' is not defined

#13 rbuckton closed 1 year ago
6
stage 1

#12 ghost closed 7 years ago
0
Rendered spec link

#11 littledan closed 7 years ago
1
Initial spec text

#10 littledan closed 7 years ago
1
coordinate operator choice with optional-chaining proposal

#9 tvald closed 1 year ago
19
Fixed typo

#8 madskonradsen closed 7 years ago
1
Is there a distinction between ?? and the elvis operator ?:

#7 samuelgoto closed 1 year ago
5
Should the `??` operator applied to `null` actually return `null` (as opposed to the default)?

#6 samuelgoto closed 1 year ago
19
Is a new operator needed?

#5 noppa closed 7 years ago
2
Symmetric operator?

#4 hax closed 1 year ago
9
Nit: "nullary" misused

#3 BrendanEich closed 7 years ago
25
[docs] Include examples not related to `?.`

#2 rattrayalex closed 5 years ago
5
a ??= b

#1 claudepache closed 6 years ago
13

Previous