Luau crash with constraint debugger "x_as_any_if_x_is_instance_elseif_x_is_table" if x is used as a function about luau HOT 4 CLOSED

This was fixed too

from luau.

also x shows up as never, I think this should become a setting, if unknown and never are a reference to any it's sooo confusing, someone explain

from luau.

unknown and never are different types, not references to any. unknown and any are very closely related though. unknown is a type that can be ascribed to any value, and any is a type that ignores any type errors it might run into. So, in practice, they look very similar, but the difference is that if you want to take something from the type unknown to a more specific type, you'll have to explicitly cast it, but any will allow you to implicitly cast to a more specific type. never, on the other hand, is the return type of functions that do not return (e.g. the built-in error function). We'll provide more documentation for all of this when we actually ship the new type solver.

from luau.

unknown and never are different types, not references to any. unknown and any are very closely related though. unknown is a type that can be ascribed to any value, and any is a type that ignores any type errors it might run into. So, in practice, they look very similar, but the difference is that if you want to take something from the type unknown to a more specific type, you'll have to explicitly cast it, but any will allow you to implicitly cast to a more specific type. never, on the other hand, is the return type of functions that do not return (e.g. the built-in error function). We'll provide more documentation for all of this when we actually ship the new type solver.

I saw that the new type solver typeof(table.clone()) outputs {+ +} now, instead of {- -}

Not sure if that's intended. It is gonna break anyone that used table.clone() for {- -} (barely anyone does that probably, other than me)

A cool thing though is that typeof({}) is now an unsealed table.

100% there's a valid usecase for doing this. e.g. creating a class where you pass a table

you access that table through class.Data however, something magical makes it sealed and this typeof method is what I use as a solution

I can even see adding support for customized properties in Roact... maybe, somehow in some way. Roact is not used anymore though.

from luau.