Welcome to the main channel on the development of MoarVM, a virtual machine for NQP and Rakudo (moarvm.org). This channel is being logged for historical purposes.
Set by lizmat on 24 May 2021.
01:12 committable6 left, coverable6 left, bloatable6 left, nativecallable6 left, unicodable6 left, linkable6 left, releasable6 left, sourceable6 left, shareable6 left, statisfiable6 left, quotable6 left, bisectable6 left, greppable6 left, squashable6 left, notable6 left, tellable6 left, evalable6 left, benchable6 left 01:13 committable6 joined, greppable6 joined, benchable6 joined, linkable6 joined, quotable6 joined 01:14 sourceable6 joined, bloatable6 joined, statisfiable6 joined 01:15 nativecallable6 joined 02:12 notable6 joined 02:13 bisectable6 joined, unicodable6 joined, shareable6 joined 03:13 linkable6 left, tellable6 joined 03:14 squashable6 joined, linkable6 joined 03:15 releasable6 joined 05:03 bloatable6 left, squashable6 left, unicodable6 left, tellable6 left, nativecallable6 left, sourceable6 left, greppable6 left, statisfiable6 left, releasable6 left, committable6 left, quotable6 left, benchable6 left, notable6 left, bisectable6 left, shareable6 left, linkable6 left 05:04 releasable6 joined 05:05 bisectable6 joined, shareable6 joined 05:06 shareable6 joined 05:15 evalable6 joined 06:03 quotable6 joined 06:04 linkable6 joined, committable6 joined, benchable6 joined 06:05 squashable6 joined, sourceable6 joined, tellable6 joined, notable6 joined 06:06 statisfiable6 joined 07:04 greppable6 joined 07:05 nativecallable6 joined 07:15 coverable6 joined 08:00 squashable6 left 08:02 reportable6 joined 08:05 bloatable6 joined 09:04 unicodable6 joined 10:00 lizmat left, TempIRCLogger left 10:12 lizmat joined 10:15 TempIRCLogger joined 11:00 squashable6 joined
timo still thinking about how to junctions with dispatchers 11:26
using resumption would perhaps allow me to only use dispatchers, which means i don't have t fiddle with capture objects and flattening, which i'm not sure how exactly the inlining deals with this at the moment 11:27
but that requires some piece of code to be in place to actually ask for resumption when one call is done, and also something to collect the results for the return value 11:28
so i think that's no bueno
with a code handling the looping, i'm not sure if dispatchers will be of much use at all? 11:29
or perhaps a dispatcher that implements "replace a single argument in the capture and invoke" could help? does that even make sense? 11:38
11:42 frost-lab joined 12:03 reportable6 left 13:04 reportable6 joined 14:04 linkable6 left, evalable6 left 15:27 dogbert11 joined 15:29 dogbert17 left 15:54 frost-lab left 15:58 frost-lab joined, frost-lab left 16:06 linkable6 joined 17:06 dogbert11 left 17:24 dogbert11 joined 17:30 dogbert17 joined, dogbert11 left 17:35 dogbert17 left 17:43 dogbert17 joined 18:02 reportable6 left 18:04 reportable6 joined 19:00 tbrowder left 19:01 tbrowder joined 20:41 dogbert17 left, dogbert11 joined
MasterDuke what arg would you replace? 20:44
20:46 dogbert17 joined 20:49 dogbert11 left 20:55 dogbert17 left, dogbert17 joined 21:00 dogbert17 left 22:07 evalable6 joined 22:20 dogbert17 joined 23:20 reportable6 left, statisfiable6 left, notable6 left, squashable6 left, benchable6 left, evalable6 left, bloatable6 left, coverable6 left, quotable6 left, sourceable6 left, greppable6 left, nativecallable6 left, tellable6 left, unicodable6 left, bisectable6 left, shareable6 left, releasable6 left, linkable6 left, committable6 left, evalable6 joined, sourceable6 joined 23:21 unicodable6 joined, tellable6 joined 23:22 nativecallable6 joined, bloatable6 joined, statisfiable6 joined 23:23 benchable6 joined, coverable6 joined, notable6 joined