🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
00:00 reportable6 left 00:02 reportable6 joined, sena_kun left 01:12 frost joined 01:26 frost left, frost joined 02:25 frost left 02:52 frost joined 05:02 [Coke]_ joined 05:04 [Coke] left 05:07 [Coke] joined, [Coke]_ left 06:00 reportable6 left, reportable6 joined 07:49 frost left 10:31 sena_kun joined 11:04 [Coke] left 11:07 [Coke] joined 11:12 frost joined 11:19 kjp left 11:32 kjp joined 11:51 tonyo left, tonyo joined 12:00 reportable6 left 12:01 reportable6 joined 12:07 ab5tract left
lizmat nine: do you have any idea why, in the BUILDPLAN, the values 1501..1510 aren't 801..810 ? 14:11
(and yes, I've started on the BUILDALL building logic 14:12
nine lizmat: no 14:19
lizmat ok, maybe something to change after RakuAST becomes default 14:20
nine Why not just keep it?
lizmat slight optimization in handling BUILDALL building 14:21
vrurg_ lizmat: just for you to know, this would break AttrX::Mooish as it is using BUILDPLAN to let have lazily initialized :D attributes. Apparently, I wouldn't complain as I rely on undocumented guts. :) 14:43
lizmat hehe... indeed :-)
vrurg_ But we don't have legal way on doing this, so... 14:44
14:44 vrurg_ is now known as vrurg
nine We have renumbered BUILDPLAN once already 14:59
vrurg And that made me add a check on Rakudo version to maintain backward compatibility. Would need one more check if renumbering happens again. 15:02
16:09 codesections joined 16:20 [Coke]_ joined 16:23 [Coke] left 16:27 [Coke]_ is now known as [Coke]
jdv can someone bump the things? looks like moarvm has newer commits than nqp points at. 16:33
lizmat but not many? 16:34
jdv no, not many 16:36
lizmat 2 basically, a helper script and an extra build option?
jdv looks like it
lizmat so you want it bumped anyways ?
jdv is there a reason not to? 16:37
be weird for releases if they didn't match up, no? 16:38
lizmat they would be done in the release, I'd say 16:39
but will bump now
jdv thanks
Geth nqp/main: 35b3029309 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION
Bump MoarVM to get latest tweaks
[Coke] better to bump *before* the release as a canary, no? 16:43
if we only bump at time of release, we're getting very little testing on those last few items.
we could be more selective we kept 'main' and 'next-release' as separate branches. 16:44
Geth rakudo/main: 92d485ee5f | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
Bump NQP to get latest MoarVM tweaks
rakudo/main: 6b6c0ec8a6 | (Elizabeth Mattijsen)++ | 2 files
Re-instate old behaviour of List.sum

And also do *NOT* special case [+] anymore. With new-disp, that optimization was probably questionable anyway. Should this show any performance regressions, we can look at that later again, or wait until RakuAST's grammar has landed.
This should address github.com/rakudo/rakudo/issues/5209 and keep github.com/rakudo/rakudo/issues/5205 happy as well.
18:00 reportable6 left 18:03 reportable6 joined 19:41 linkable6 left 19:43 linkable6 joined 19:55 discord-raku-bot left, discord-raku-bot joined 20:00 NemokoschKiwi joined 20:01 NemokoschKiwi left 20:22 Xliff joined 20:33 lucs joined 21:09 ab5tract joined 21:15 codesections left 21:50 frost left, codesections joined 21:53 ab5tract left 22:28 sena_kun left 22:29 Xliff left 23:05 Geth left, RakuIRCLogger left 23:06 codesections left 23:17 codesections joined