It's definitely possible there are bugs, it's a fairly new and complex beast, but I don't think it's that bad. Can you share some (preferably minimal) example code which demonstrates this issue?

Is it possible, for a future version, to implement a mechanism for reporting thread errors that works like an exception instead of an event? No, because lua itself isn't thread-safe. There is no way to interrupt the main thread, so it has to poll, in this case via the event loop. Or maybe a way to ...

Yeah, the only way around that is to load the thread contents later, I guess. Something like: local channel, contents = ... local ok, err = pcall(function() loadstring(contents)(channel) end) if not ok then channel:supply{error = true, data = err} end (Or pass a filename and call love.filesystem.loa...

It's already been lifted for 0.11.0, and it will error if it detects cycles (instead of go into an infinite loop/overflow the stack). It's still a very basic copying mechanism though, and I wouldn't be surprised if some lua serializers outperform it.

Because of a bug you can actually push nested tables (though it won't detect cycles) in 0.10.2. Otherwise, if the returned data can be arbitrary you can really only do a double push (or use a second channel). If the data is a specific type you can return an error directly, or nil, or something like ...

I believe this is because the main thread reaches channel:demand() before the thread encounters the error. The main thread is now blocked, waiting for data on the channel; the thread can't supply data because of the error; love.threaderror doesn't get called because the main thread is blocked. Tota...

The problem is that you can only have varargs as the last argument(s). So if you rewrite your function like this, it won't error: function poly(color, ...) local edges = {...} end (Note that color is already a local, as it is an argument, so 'local color = color' doesn't actually do anything useful.)

I don't think you need to compile torch into love, just stick the dll (compiled for lua 5.1) next to the exe and require torch.

I did some googling and came across this forum post. Is your compositor backend set to OpenGL 2.0, and if so, can you try setting it to OpenGL 3.1?

The shadows for my KDE panels disappear, [...] and it looks like some windows have a black square being rendered behind them. So it sounds like it's your compositor that breaks, somehow. In case you don't know, the compositor is the part of the (x11) graphics stack that implements transparent windo...