vegorov-rbx

Sorry for the long response, we had to find someone who knows how CMake works. This change will result in anything downstream from `Luau.CodeGen` that relies on LUACODEGEN_API having to...

@zeux I wonder if we should always use "C" linkage without relying on CMake and place them in a block like: ```c++ #ifndef __cplusplus extern "C" { #endif ```

While we might add more `os` library methods/IO/dynamic modules in the future specifically for luau build as an executable, right now we don't have this on our roadmap. Like it...

As a work-around, I would recommend just helping out the inference by providing `local a: {string}`.

To explain one of the parts: ``` type BST = { Add: (self: BST, value: T) -> boolean, Remove: (self: BST, value: T) -> (), Iter: (self: BST, value: T)...

> -- The follow function doesn't provide a type-check error > -- I expect `: (nil)` to expect a `return nil`, instead of returning conceptual 'void' This part of the...

Is there something wrong with current releases? https://github.com/luau-lang/luau/releases

``` type Iterable = typeof(setmetatable( {}, {}::{ __iter: (self: Iterable) -> () -> (number, string) } )) local t: Iterable for a, b in t do end ```

This happens when error was generated at a point where type wasn't known to be `ConnectionObject?`. I would suggest adding a type annotation to avoid the error: ``` type Function...

If we were to add this, it should work through a .luaurc file so that any tool can be aware of the dependency: https://github.com/luau-lang/luau/issues/418