Perl 6 - the future is here, just unevenly distributed

IRC log for #moarvm, 2016-08-21

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:47 ilbot3 joined #moarvm
01:47 Topic for #moarvm is now https://github.com/moarvm/moarvm | IRC logs at  http://irclog.perlgeek.de/moarvm/today
02:28 lizmat joined #moarvm
04:01 lizmat joined #moarvm
04:56 ggoebel joined #moarvm
05:33 lizmat_ joined #moarvm
06:25 domidumont joined #moarvm
06:29 domidumont joined #moarvm
07:04 lizmat joined #moarvm
07:31 TheLemonMan joined #moarvm
10:43 domidumont joined #moarvm
11:00 synopsebot6 joined #moarvm
12:31 domidumont joined #moarvm
14:00 zakharyas joined #moarvm
16:50 zakharyas joined #moarvm
17:31 domidumont joined #moarvm
17:41 timotimo http://nekovm.org/  -  i wonder if this has anything interesting in it?
17:47 timotimo http://nekovm.org/doc/nxml  -  they have their own way of writing asts directly in their code, like our nqp::stmts and such nodes
17:50 timotimo their FAQ contrasts neko vs parrot
17:51 timotimo Neko is using the Boehm GC, which is a conservative multithreaded mark and sweep collector. However, since all calls to the GC are wrapped by the Neko API in vm/alloc.c, it might be possible to easily switch to another garbage collector in the future.
17:51 timotimo that's cute :P
18:33 zakharyas joined #moarvm
18:35 jnthn I'd guess a bunch of options will run into needing write barriers.
18:35 jnthn "a single VM shouldn't be used to execute code on several threads at the same time."
18:36 jnthn Guess we won't be borrowing any neat threading ideas :)
19:00 vendethiel joined #moarvm
19:49 brrt joined #moarvm
19:59 brrt interesting thing
20:30 ggoebel joined #moarvm
20:31 lizmat joined #moarvm
20:32 leego joined #moarvm
20:41 lizmat joined #moarvm
21:13 lizmat joined #moarvm
21:28 synopsebot6 joined #moarvm
23:22 japhb What's the MoarVM idiom for writing out debugging info, akin to fprintf(stderr, ...) but safe WRT threads, GC, libuv, etc.?
23:25 japhb I'm trying to figure out the problem with getting Malformed UTF-8 on binary stdout from an async proc, and I can't see where the binaryness is getting lost, so now I'm going to try debug output ...
23:35 * geekosaur had been wondering... was it stdout, or stderr?
23:35 japhb stdout
23:37 japhb Thankfully, all the IO happens on a single thread, so I won't get a complete mess in the debug output, but it is callback-and-bespoke-structure hell because libuv, so it will be "interesting" to figure out.

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary