Tim Caswell
Tim Caswell
I think it makes sense that the luvit script doesn't normally see the luvit flags in it's args list. We can expose them (preparsed even) as some named property on...
Lua is tricky in this regard. If you "rethrow" an error, it will get a new stack trace. Or perhaps I'm not understanding lua. I do know that JavaScript doesn't...
No need for `assert(false, ...)` just do `error(...)`. I don't see how an unexpect would help, it would just internally call `error()` right?
I think a simple `error("this should not have happened because...")` is plenty explicit. The issue about uncaught errors causing fatal exist is a problem though. I'll think about a way...
I've love a luvit benchmark using the coro-\* APIs. They are generally lower abstraction than the node-style streams based APIs. (of course you could always use raw libuv like in...
This would be cool. I don't think `luvi` would place in this world, but `lit` and `luvit` could certainly be luarocks scripts using the same libraries we have today. I've...
I ran into this as well. The problem had to do with how shells connect the file descriptors when the input is a file. It's a limitation of libuv itself...
https://github.com/libuv/libuv/issues/281
See also https://github.com/luvit/luv/issues/126
Circular requires were implemented because originally luvit was a port of node.js where it's explicitly supported.