Luau performance buff?

[waves5217 (waves)]

Luau Type Checking Release:

@zeuxcg

• nocheck, where we don’t type check the script in question.
• nonstrict, where we type check the script but try to be lenient to allow commonly seen patterns even if they may violate type safety
• strict, where we try to make sure that every single line of code you write is correct, and every value has a known type.

Green usually appears when return type doesn’t match, and orange when there are typos, or the key doesn’t exist or mismatches the assigned type.

Also:

Luau Type Checking Release:

@zeuxcg

Right now type annotations are ignored by our bytecode compiler; this means that performance of the code you write doesn’t actually depend on whether you use strict, nonstrict or nocheck modes or if you have type annotations.

This is likely going to change! We have plans for using the type information to generate better bytecode in certain cases, and types are going to be instrumental to just-in-time compilation, something that we’re going to invest time into next year as well.

Today, however, there’s no difference - type information is completely elided when the bytecode is built, so there is zero runtime impact one way or another.