You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Second two...we effectively see those are the same.
Intent of last one isn't clear.
Need missing.
Half of the world's undefined is missing and half is still undefined.
Probably fine to skew towards not including undefined.
Reminds of "safe any"
missing < undefined
... void < undefined?
Can you use void?
Sadly no.
Hard to guess how breaky the world would be.
Have to just see.
The current "optimistic" strategy in the PR seems good. People who badly want to deal with undefined in these cases may just want --noUncheckedIndexedAccess.
Exclude enum/number compatibility rule from comparable relation
Remove
undefined
from Optional Properties When Inferring to Index Signatutres#43086
missing
.undefined
ismissing
and half is stillundefined
.undefined.
any
"missing
<undefined
void
<undefined
?void
?undefined
in these cases may just want--noUncheckedIndexedAccess
.Exclude enum/number compatibility rule from comparable relation
#42472
Efficiency in Narrowing Generics
T extends unknown
can be checked against=== "foo"
, but a bareT
with no constraint is allowed.===
,.includes
, etc. But then you allow a big class of mistakes of relating unrelated entities.number <-/-> string
errors, those aren't as questionable.The text was updated successfully, but these errors were encountered: