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
You've got a ton of object literals with a texto and a sentimento, and a unique property with the same text as texto.
The type-checker goes through the array literal and tries to apply subtype reduction; however, each of those unique properties makes each object type distinct, so none of them is a subtype of any other type.
Even if we get through the extremely long subtype reduction pass, we apply a normalization pass when dealing with unions of fresh object types, so with n objects with unique properties, each object type is "blessed" with those unique properties being set to the undefined type.
We have a problem where the language service just doesn't die gracefully.
We can try to fix the problem, or we can find a way to tell users that something's going wrong.
Trailing commas on tuples
#28893
A smarter strict signature for
bind
#28900
strictBindCallApply
, we have a few limitations withbind
/call
/apply
:{}
(or their explicit constraint).bind
are just to bind the argument ofthis
.this
when function types don't event declare theirthis
type?bind
?this
.Could imagine a
bind
is already a method on functions, why do we need constraints?Handling huge type relationship checks and normalization
#28540
texto
and asentimento
, and a unique property with the same text astexto
.n
objects with unique properties, each object type is "blessed" with those unique properties being set to theundefined
type.undefined
properties inside actual types #28727)any
here".The text was updated successfully, but these errors were encountered: