sena_kun what's the tool for bumping? 12:09
and what's the policy for bumping?
nine .bothelp 12:32
.help
.bots
releasable6: help 12:33
releasable6 nine, status | status link # See wiki for more examples: github.com/perl6/whateverable/wiki/Releasable
nine sena_kun: I've only ever bumped manually. Policy seems to be "whenever it seems to make sense to you" 12:34
sena_kun nine: I see, thanks, the messages look as generated ones... there is nothing wrong with bumping to latest moar to get some fixes? I see a mention of a new bug, but if it has a workaround, I'd like to go for it. 12:35
nine sena_kun: do you have any idea on when the MoarVM release will be made? If it's within the next day, I'd like to commit my workaround first. 12:36
sena_kun nine: my plan for today is either 1)get fresh fixes, count this revision as "we'll do a release from that" and then check stuff for regressions; 1)get old (six days old) version we have blin results for already and make a release out of it. 12:37
AlexDaniel sena_kun: this is the only tool: github.com/perl6/z 12:38
sena_kun I'd go for a first one, so yes, I can wait for a workaround
AlexDaniel, I see, thanks 12:39
nine sena_kun: ok, then I'll definitely commit the workaround :)
sena_kun nine: +1
Geth_ nqp: ac4b11d438 | (Stefan Seifert)++ | tools/templates/MOAR_REVISION
Bump MoarVM for NativeCall fixes
13:01
rakudo: 6bc64c7132 | (Stefan Seifert)++ | tools/templates/NQP_REVISION
Bump NQP for NativeCall fixes
nine sena_kun: ^^^
lizmat pulls, builds and spectests 13:02
lizmat all clear 13:21
Geth_ rakudo: b6afa71277 | (Elizabeth Mattijsen)++ | src/core.c/Rakudo/Iterator.pm6
Add is-lazy named to `gather` iterator

So that the underlying iterator *can* be told to act as a lazy iterator. Now all we need is a syntax to mark a `gather` block as lazy. This in response to #3380
13:37
lizmat m: role A { method a() { 666 } }; class B does A { has $.a = 42 }; dd B.new.a 13:59
camelia 666
Xliff Merry Christmas, #raku!
lizmat that feels wrong to me
Xliff o/
Merry Xmas is not what feels wrong to me :-)
Xliff lizmat: Yeah, there should be some warning there, but that's really a case of a badly named override.
lizmat I think it's a wrongly handled override 14:00
Xliff More like a badly named method that's causing an unintended override?
lizmat m: role A { method a() { 666 } }; class B does A { has $.a = 42; method a() { $!a } }; dd B.new.a
camelia 42
lizmat if I declare an attribute to be public, it should override anything that the role provided 14:01
Xliff And I would expect that last one to at least throw a warning!
lizmat I think the check for creating the accessor is faultry
*faulty
Xliff And I would say you have a very good point! 14:02
lizmat: So what brings you to IRC on this fine day?
lizmat a love/hate relationship with this particular date ?
Xliff Ah.
lizmat mostly hate 14:03
Xliff EEp.
lizmat it's why I celebrate my birthday on 21st of June :-)
Xliff Hopefully you and yours will have a nice get-together for dinner, at least. 14:04
lizmat had that yesterday :-)
Xliff Oh, good.
lizmat still stuffed :-)
Xliff Heheh
Something tells me I will be back into the guts of Method::Also, today.
lizmat did you see my update? 14:05
Xliff Guess not. When did that happen? 14:06
lizmat on Monday, to fix a release blocker
Xliff Looking 14:07
Hah! I missed that! 14:08
lizmat: What was the blocker?
lizmat that Method::Also did not install :-) 14:09
Xliff Odd. I hadn't beeen having problems with the old code.
Maybe exposed via newer rakudo?
lizmat yeah, I think it's related to vrurg's role work
Xliff Ah! OK. 14:10
Was hoping I could leverage that into a better solution. Now role-based aliases are not showing up in my code.
lizmat well, I guess you need to figure that out with vrurg :-) 14:12
Xliff lizmat: Yeah.. this bug is mine... github.com/lizmat/Method-Also/comm...15c09b0R57
lizmat ok, well looking forward to your fix then :-) 14:13
Xliff Hahahahaha!
Me too!
Geth_ rakudo: 07072f3803 | (Elizabeth Mattijsen)++ | 2 files
Introduce :is-lazy named for gather { } blocks

After this commit, you can indicate that your `gather` block is to be treated as a lazy one:
   gather {
   ...
   } :is-lazy;
14:14
Xliff lizmat: Well, the big problem preventing that fix is the fact that this code never executes and I can't figure out why: github.com/lizmat/Method-Also/blob...so.pm6#L27 14:18
I since moved it to incorporate_multi_methods and it's still not working. 14:19
So... I guess next step is easy.
Geth_ rakudo: 8e3b0a7144 | (Elizabeth Mattijsen)++ | 2 files
Revert "Introduce :is-lazy named for gather { } blocks"

This reverts commit 07072f380327db9b118cab4a2babc33ba73c683c.
We actually have syntax for lazy gather blocks: it's called:
   lazy gather {
   ...
   }
  jnthn++
14:22
Geth_ rakudo: 55d0143e2b | (Elizabeth Mattijsen)++ | src/core.c/Rakudo/Iterator.pm6
Revert "Add is-lazy named to `gather` iterator"

This reverts commit b6afa71277c6f0405a1fb31976fb8aa70310b5a3.
This is not going to be used, so remove it.
18:27
rakudo: 971174f4d8 | (Elizabeth Mattijsen)++ | src/core.c/Iterable.pm6
Make `lazy gather` up to 15% faster

By using nqp::ifnull to see whether there has been an iterator created already. The benchmark is for:
   lazy gather { .take for ^500000 }
so very light on what is actually been gathered. So your actual mileage will vary.
18:51
rakudo: e8a9e07fd2 | (Elizabeth Mattijsen)++ | 2 files
Move the Lazy iterator class to Rakudo::Iterator

To make it more in line with other iterators that live there. And more generally available, should that be needed. And add some comments.
19:10
lizmat .ask jnthn what was the reason for implementing "lazy" as an Iterable method called by codegen magic, rather than as a sub ? 19:13
tellable6 lizmat, I'll pass your message to jnthn
lizmat .ask jnthn I guess the same goes for "hyper" and "race" 19:17
tellable6 lizmat, I'll pass your message to jnthn
Geth_ rakudo: 17d8116069 | (Elizabeth Mattijsen)++ | src/core.c/Iterable.pm6
Don't need to create a Seq object when recursing in flat
19:42
rakudo: d5a34f19f5 | (Elizabeth Mattijsen)++ | 2 files
Move the Flat iterator class to Rakudo::Iterator

To make it more in line with other iterators that live there. And more generally available, should that be needed. And add some comments.
20:03
AlexDaniel sena_kun: fwiw this is the repo for working on alwaysfails: github.com/perl6/ecosystem-unbitrot 21:59
sena_kun: the issue tracker can be updated by using the data.json file and a script somewhere
sena_kun: I can do it but only if we don't have too many erroneous alwaysfails… 22:00