|
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:32
guifa left
01:34
guifa joined
02:21
guifa left
02:37
guifa joined
04:08
guifa left
09:16
lizmat left,
lizmat_ joined
09:17
lizmat_ left
09:18
lizmat joined
|
|||
| lizmat | still thinking about github.com/rakudo/rakudo/issues/5826 | 09:30 | |
| and I wonder: at the MoarVM level, there is no difference between a "sub" and a "multi sub" code block, right? | 09:31 | ||
| aka, the issue context capture issue cannot be in the VM? | 09:32 | ||
| nine | right | 09:37 | |
| lizmat: I think #5826 just cannot work as intended. If we look at what multi dispatch does conceptually. We call a proto. That proto goes through its list of candidates, picks the most appropriate one and calls this. The list of candidates is a property of the proto itself. | 10:47 | ||
| That candidates list will contain the multi candidates as they are declared originally. They are not closure clones! | 10:48 | ||
| To fix it you'd have to also create clone of that candidates list and have each element itself be a clone with the closure propagated. | 10:49 | ||
| lizmat | ok, then I'll propose a workaround | 10:58 | |
|
12:18
guifa joined
13:08
guifa left
|
|||
| [Coke] | I still need write access to moarvm.org's repo. jnthn1, any chance you can sort for me so the release is smooth tomorrow? | 21:21 | |
| worst case, jdv, will need you to approve a PR for me again tomorrow. | |||
|
21:56
guifa joined
|
|||