ariel
That is a bug then, I'll adjust your issue description.
What do you mean by "too eager?" This error corresponds to hitting internal limitations in certain places, it's certainly fair to say "i feel like it is too restrictive for...
This probably has absolutely nothing to do with Roblox data types. My immediate best guess is that this is a problem with some of the expected type code, but we'll...
The expected behavior for both of these is that the intersection is `never` because table types and extern types are disjoint, and so have no common values, but we have...
This is not a bug if you expect it to work in general, though we can and should allow this particular case because the table is a literal in that...
It has nothing to do with Roblox type definitions, but yes, `{ ... }` is a table literal expression. The table does not exist before that point. So, that example...
This is caused by refinements producing intersections between the class types and table types with the specified properties, and then normalization is turning any intersection of a class with a...
#1862 is a similar request for an annotation that would cause a parameter type to be enforced at runtime, but it's not technically the exact same request. To actually be...
Variable's type sometimes unions with `nil` due to `if` statement with new type solver's strict mode
Here is some context about why this is happening. There's currently an affordance that indexing a table with an indexer returns a non-`nil` type. This is present because (at some...
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.