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.
00:02 reportable6 left 01:02 reportable6 joined 02:02 linkable6 left, evalable6 left 02:03 evalable6 joined 02:05 linkable6 joined 02:39 vrurg left 02:41 vrurg joined 03:10 jgaz joined 03:15 jgaz left 05:05 reportable6 left, sourceable6 left, squashable6 left, notable6 left, tellable6 left, committable6 left, bisectable6 left, coverable6 left, benchable6 left, evalable6 left, unicodable6 left, shareable6 left, greppable6 left, nativecallable6 left, bloatable6 left, releasable6 left, quotable6 left, statisfiable6 left, linkable6 left 05:06 shareable6 joined, coverable6 joined 05:07 unicodable6 joined, greppable6 joined, squashable6 joined, bloatable6 joined, committable6 joined 05:08 evalable6 joined, quotable6 joined, statisfiable6 joined, reportable6 joined 06:02 leedo_ left, leedo joined, reportable6 left 06:06 sourceable6 joined, nativecallable6 joined, tellable6 joined 06:07 bisectable6 joined 07:05 reportable6 joined 07:07 linkable6 joined, releasable6 joined
Nicholas good *, * 07:12
07:34 frost joined 07:55 dogbert12 left 08:07 benchable6 joined 09:06 notable6 joined
timo good -> $a, $b { $a, $b } 09:53
moon-child good { $^a, $^b } 09:55
lizmat good *,* ? 10:26
10:30 evalable6 left, linkable6 left 10:44 Colt left 10:59 Colt joined 11:33 evalable6 joined 11:34 Altai-man joined 12:02 reportable6 left 12:04 reportable6 joined 12:31 linkable6 joined 14:32 frost left 15:03 nebuchadnezzar left 15:27 Geth joined
japhb lizmat: Kinda looks like an owl face 15:28
lizmat :-)
18:02 reportable6 left
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2021/11/29/2021-...sdem-2022/ 18:33
18:51 Altai-man left 18:59 squashable6 left
lizmat m: my str $a; BEGIN { $a = "foo" } # is this a known issue ? 19:14
camelia 5===SORRY!5=== Error while compiling <tmp>
An exception occurred while evaluating a BEGIN
at <tmp>:1
Exception details:
5===SORRY!5=== Error while compiling
Lexical with name '$a' has wrong type. real type 8 wanted type 7
lizmat m: BEGIN my str $a = "foo" # golf 19:15
camelia 5===SORRY!5=== Error while compiling <tmp>
An exception occurred while evaluating a BEGIN
at <tmp>:1
Exception details:
5===SORRY!5=== Error while compiling
Lexical with name '$a' has wrong type. real type 8 wanted type 7
lizmat m: my str constant $a = "foo"; dd $a # this appears ok
camelia "foo"
lizmat also strange: 19:34
m: my %h := BEGIN { my %m is Map = a => 42, b => 666 }; BEGIN { dd %h.keys }; dd %h
camelia ().Seq
lizmat so one BEGIN time is not another ?
ugexe i was thinking it would have to be `BEGIN my %h := ...` but that doesn't do what i expect either 19:50
m: BEGIN my %h = my %m is Map = a => 42, b => 666; BEGIN { dd %h.keys }; dd %h.keys 19:55
camelia ("a", "b").Seq
("a", "b").Seq
ugexe assignment worked though 19:56
lizmat yeah, but that just makes %h a Hash
mutable and all
20:04 reportable6 joined 21:39 camelia left, japhb left, bartolin_ left, harrow left, linkable6 left, evalable6 left, benchable6 left, Kaiepi left, Nicholas left, leont left, jnthnwrthngtn left, rba left 21:41 Colt left, Colt joined 21:44 linkable6 joined, evalable6 joined, benchable6 joined, japhb joined, Kaiepi joined, Nicholas joined, bartolin_ joined, camelia joined, leont joined, jnthnwrthngtn joined, harrow joined, rba joined 21:45 Colt left 21:46 Colt joined 22:05 nebuchadnezzar joined
jnthnwrthngtn lizmat: BEGIN-time bindings aren't preserved, only assignments (and native assignment is effectively binding, or more to the point, there's no container) 22:09
japhb jnthnwrthngtn: Why aren't BEGIN-time bindings preserved? 22:11
jnthnwrthngtn The lexical scope surrounding the BEGIN isn't compiled at the time the BEGIN block is, so we have to fake it up, and we don't cheat hard enough to preserve bindings, just hard enough that the "prototype" container is preserved 22:28
japhb Ah interesting 22:30
jnthnwrthngtn I suspect RakuAST will take a different approach to all of this
japhb Is PEA or RakuAST first on your agenda for the new year? 22:31
jnthnwrthngtn I don't think it's impossible to make it work (and don't doubt it ideally would work), just wouldn't fancy doing it on the current compiler architecture :)
japhb Gotcah
jnthnwrthngtn Probably a bit of both, though I suspect PEA will be the one that finishes first :)
Plan to do the re-work of LEAVE-time ahead of either of those (though hoping to do that in December) 22:32
japhb What will that rework gain us? 22:34
jnthnwrthngtn Much cheaper LEAVE handling, removal of some icky scope hackery, and hopefully a fix for a long-standing bug where return values get messed up sometimes when using LEAVE blocks 22:44
While one may not directly use LEAVE very much, it is used in Lock and Lock::Async, for example 22:45
23:03 squashable6 joined
japhb Oh, and that's definitely going to end up used a lot in concurrent code (often implicitly, I suspect). 23:18
23:24 squashable6 left 23:25 squashable6 joined