Take this simple childrenof type function for example, which should be a near-equivalent to the keyof function, expect it creates an union of the instance’s children names.
If you were to put a contradicting comparison, say that if type was a singleton even if it was a class type and return an arbitrary type, it would break the type solver across all place files shown by that orange bar when used. This renders autocomplete and typechecking completely useless.
This bug can be fixed by deactivating and then re-enrolling back to the Luau type solver beta, but the behavior makes no room for mistakes and that you’ll have to be extra careful when dealing with type logic regardless if this is intentional or not.
Expected behavior
I expect the type function to simply error when that is already the case in runtime code, when the linter would claim that this is impossible to do.
