github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
dogbert17 .seen nine 17:40
tellable6 dogbert17, and I oop! Backtrace: gist.github.com/768354f07ae2d75a3a...f7480c61e1
dogbert17 heh
m: await ^1000 .map: {start '{my $x}'.EVAL}; say "all good" 17:43
camelia ===SORRY!===
Decoder may not be used concurrently
vrurg dogbert17: EVAL isn't thread sage, long known issue. 18:08
dogbert17 vrurg: I know. just wanted to check with nine since he has, if I remeber correctly, been looking into the 'Decoder may not be used concurrently' issue 18:14
*remember 18:15
vrurg Basically, decoder is the only known problem to me. Currently EVAL is utilyzing same compiler instance it gets with getcomp. But it shouldn't be a big deal to create and use a new one. 18:16
AlexDaniel .seen nine 18:36
tellable6 AlexDaniel, I saw nine 2019-10-30T19:02:54Z in #raku-dev: <nine> kelly: that's really hard to answer in a general way.
AlexDaniel dogbert17: ↑ :)
dogbert17 so, is it ok for two threads to be garbage collecting at the same time? 19:42
japhb That's the normal state of things during a GC run. 19:46
japhb (They are properly coordinated for blocked and active threads, too.) 19:47
dogbert17 japhb: thx 20:03

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!