Luau is our new language that you can read more about at https://luau-lang.org.
Semantic subtyping
One of the most important goals for Luau is to avoid false positives, that is cases where Script Analysis reports a type error, but in fact, the code is correct. This is very frustrating, especially for beginners. Spending time chasing down a gnarly type error only to discover that it was the type system that’s wrong is nobody’s idea of fun!
We are pleased to announce that a major component of minimizing false positives has landed, semantic subtyping, which removes a class of false positives caused by failures of subtyping. For example, in the program
local x : CFrame = CFrame.new()
local y : Vector3 | CFrame
if (math.random()) then
y = CFrame.new()
else
y = Vector3.new()
end
local z : Vector3 | CFrame = x * y -- Type Error!
an error is reported, even though there is no problem at runtime. This is because CFrame ’s multiplication has two overloads:
((CFrame, CFrame) -> CFrame)
& ((CFrame, Vector3) -> Vector3)
The current syntax-driven algorithm for subtyping is not sophisticated enough to realize that this is a subtype of the desired type:
(CFrame, Vector3 | CFrame) -> (Vector3 | CFrame)
Our new algorithm is driven by the semantics of subtyping, not the syntax of types, and eliminates this class of false positives.
If you want to know more about semantic subtyping in Luau, check out our technical blog post on the subject.
Other analysis improvements
- Improve stringification of function types.
- Improve parse error warnings in the case of missing tokens after a comma.
- Improve typechecking of expressions involving variadics such as
{ ... }. - Make sure modules don’t return unbound generic types.
- Improve cycle detection in stringifying types.
- Improve type inference of combinations of intersections and generic functions.
- Improve typechecking when calling a function that returns a variadic e.g.
() -> (number...). - Improve typechecking when passing a function expression as a parameter to a function.
- Improve error reporting locations.
- Remove some sources of memory corruption and crashes.
Other runtime and debugger improvements
- Improve performance of accessing debug info.
- Improve performance of
getmetatableandsetmetatable. - Remove a source of freezes in the debugger.
- Improve GC accuracy and performance.
Thanks
Thanks for all the contributions!
