SinisterRectus
SinisterRectus
If you're running into a require cycle, then you may want to reconsider your module design. If you absolutely cannot do this, you can foward declare the module and require...
Interesting. I convinced myself that Luvit's circular requires do not work because they weren't supposed to work.
Related issue? https://github.com/luvit/lit/issues/199
Maybe it's time to start considering [luvit 3.0](https://github.com/luvit/luvit/issues/857#issuecomment-519516350).
Cannot reproduce on Windows using luvit 2.16.0 or GitHub master. Is this still an issue? I don't have access to Linux at the moment.
How about keeping an array of the functions and indexing them with `mode`?
@halfnelson Try disabling jit with [jit.off](http://luajit.org/ext_jit.html) before using the hook. I ran into a similar problem with this. I'm not sure if it's the same issue. ```lua local code =...
After the 2.0 rewrite, I think that Luvit has largely been community-driven, with up to 5 people making most of the decisions and contributions. It's mostly been maintenance with occasional...
I think this is an issue with ```lua local mq = require("cluster/mq") ``` Try changing it to ```lua local mq = require("./cluster/mq") ```
Hmm. Alright. I'll take a closer look at the code to see if I can get otherwise consistent require behavior in a thread. Thanks!