Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
GMP support.
|
|
somewhere in the stack. Making the 'buffer' more persistent.
|
|
collector is a very bad idea.
|
|
back and forth because of CPU usage.
|
|
|
|
|
|
|
|
|
|
operation probably should become async...
|
|
|
|
|
|
|
|
|
|
calls in resume().
|
|
exec() call interruptible.
|
|
|
|
only case you'd want EAgain is when an operation is yielding.
|
|
lua_error on a yielded co-routine.
|
|
|
|
|
|
|
|
|
|
otherwise it'll always re-trigger and won't throw an EAgain, as intended.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Handle using readU8. We'll switch readU8 to use a Future.
|
|
to simple.
|
|
|
|
|
|
|
|
|
|
|
|
much broken when using stackless operations.
|
|
|
|
|
|
callback system by using the Lua's C closure mechanism.
|
|
well as as the class name.
|
|
|
|
|
|
|
|
template means pushing a table by its name, and the constructor is implicit in it.
|
|
|