Vasiliy Tereshkov

I think @robloach may already have something like this. He was working on Umka bindings for raylib: https://github.com/robloach/raylib-umka

@skejeton I think you mean #199. Yes, it's related, but not the same. There are many ways to produce a reference cycle involving a local variable. What distinguishes the current...

@skejeton I get no error in this case: ``` type Color = int const ( white* = Color(255) ) type Platform = int const ( Unknown* = Platform(0) Linux* =...

Because it is _not_ a type alias, but a declaration of a new type. If you have two named types, they can only be explicitly converted to each other: `mymod.f([]mymod.s64(xs))`....

@luauser32167 What use cases do you know? For me, an infinite loop should be infinite. If it's a programmer's mistake, the program can be terminated with Ctrl + C.

Doesn't seem very useful for any known use cases.

@marekmaskarinec Do you mean that the file dialog blocks the main application when run in the same OS thread? If so, then you cannot process them simultaneously with Umka fibers....

In contrast, a Lua->C->Lua call chain is quite possible: ``` int l_loop (lua_State *L) { for (;;) { lua_pushvalue(L, 1); lua_call(L, 0, 1); if (lua_isnil(L, -1)) break; printf("%s\n", lua_tostring(L, -1));...

The problem is not that trivial, as such call chains imply recursive calls to `vmLoop` in the current Umka implementation.

Yes, the compiler (not only the type checker) always stops on the first error and does not try to recover.