🦋 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: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
releasable6 Next release in ≈2 days and ≈11 hours. 4 blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 07:00
lizmat Files=1349, Tests=117873, 310 wallclock secs (35.10 usr 9.44 sys + 4292.81 cusr 354.31 csys = 4691.66 CPU) 09:16
Geth rakudo: dba8dbb04f | (Elizabeth Mattijsen)++ | IN-MEMORIAM.md
Add In Memoriam stub for David H. Adler
09:59
rakudo: eb837deefa | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 2 files
Remove support for use experimental :collation (#4616)

It is now supported by default, and was marked to be deleted in 2019, so seems to have ample sunsetting time for this feature.
10:38
Geth rakudo: ad145b4c5b | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/IterationBuffer.pm6
Add a IterationBuffer.new(iterable) candidate (#4599)

To facilitate initializing iteration buffers. Makes
   IterationBuffer.new(<a b c d e f g h i j>);
about 2x as fast as:
   my $b := IterationBuffer.new;
   $b.push($_) for <a b c d e f g h i j>;
   $b
10:39
Geth rakudo: 5f8441024f | MasterDuke17++ (committed using GitHub Web editor) | 2 files
Disallow cmp with a Junction (#4618)

Disallow comparing Junctions
There's no way to collapse them into a valid Order.
10:43
Geth rakudo/update-release-guide: 5d1392d8b9 | Altai-man++ | docs/release_guide.pod
Update Release Guide to have actual information
12:04
rakudo: b3b4ca2185 | Altai-man++ (committed using GitHub Web editor) | docs/release_guide.pod
Update Release Guide to have actual information (#4639)

Thank you Oleksandr Kyriukhin!
12:07
Altai-man github.com/MoarVM/MoarVM/pull/1599 wants the same treatment maybe? 12:08
lizmat :-) 12:10
Altai-man lizmat++
lizmat ugexe nine module precomp question 13:13
if I have module Foo installed
and working on module Bar, testing that with -Ilib or -I. , should it re-precompile module Foo in lib/.precomp / .precomp ? 13:14
if it shouldn't, then we have a problem here, because it looks like it does 13:29
I found out that after a Rakudo update, testing some module would fail because OO::Monitors would have a version mismatch 13:30
nuking the lib/.precomp dir solves that for me
Geth rakudo/revert-4618-disallow_cmp_with_a_Junction: 8600f5f193 | (Vadim Belman)++ (committed using GitHub Web editor) | 2 files
Revert "Disallow cmp with a Junction (#4618)"

This reverts commit 5f8441024f56d9bb29535bf3146f44aead807ea1.
14:09
rakudo: 0aba016ce1 | (Elizabeth Mattijsen)++ | 2 files
Revert "Disallow cmp with a Junction (#4618)"

This reverts commit 5f8441024f56d9bb29535bf3146f44aead807ea1.
14:20
vrurg lizmat: with regard to sort performance on junctions, it shouldn't be slower than the multi-dispatch we currently do on cmp. And it could be done with with `nqp::eqaddr` which must be cheaper than `istype`. 15:00
lizmat it's an extra check on *every* value that needs to be sorted, though 16:36
www.reddit.com/r/rakulang/comments...g_on_here/ # problem with supplies 16:50
japhb wonders if the poster wanted Supplier::Preserving there 16:52
gfldex japhb: The docs don't really explain when to use a Supplier, Supplier::Preserving or a Channel. 17:43
Geth rakudo: 74c8c861fe | (Elizabeth Mattijsen)++ | src/core.c/Date.pm6
Make Date.new(year,month,day) about 40% faster

By reducing the error checking in the method itself as little as possible, and do the full awesome error generation in a separate private method. This brings !SET-SELF under the inlining limit, thus making it 40% faster. Alas, the subclass version did not reach that limit yet, so not a lot to be gained there.
18:22
[Tux] Rakudo v2021.10-107-g74c8c861f (v6.d) on MoarVM 2021.10-72-gb744f8640
csv-ip5xs0.870 - 0.911
csv-ip5xs-205.323 - 5.470
csv-parser4.102 - 4.238
csv-test-xs-200.409 - 0.411
test7.161 - 7.265
test-t1.669 - 1.758
test-t --race0.962 - 0.995
test-t-2024.516 - 25.061
test-t-20 --race7.446 - 7.538
18:41
Geth rakudo: b994c6bbbe | (Stefan Seifert)++ | src/Perl6/Actions.nqp
Fix CATCH blocks setting $! leading to serialization errors with BEGIN time exceptions

According to the docs $! only ought to be set by try blocks or statement prefixes. CATCH blocks are supposed to only set $_ to the exception within the block. Setting $! is not just wasteful but doing so at BEGIN time may keep the exception referenced after being handled and prevent serialization.
19:17