🦋 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:01 reportable6 joined 00:09 codesections left 00:14 MasterDuke joined 01:14 linkable6 left, evalable6 left 01:15 linkable6 joined 01:16 evalable6 joined 02:40 patrickb left 02:46 patrickb joined 04:46 linkable6 left, evalable6 left 04:47 evalable6 joined 04:48 linkable6 joined 05:09 MasterDuke left 05:10 MasterDuke left 06:00 reportable6 left 06:02 reportable6 joined 06:10 kurahaupo joined 07:46 sena_kun joined 08:26 sena_kun left 08:34 kurahaupo left 08:53 notable6 left, statisfiable6 left, bisectable6 left, heartburn left 08:54 bisectable6 left, heartburn left 08:55 rypervenche left 08:56 heartburn joined 08:57 rypervenche joined 09:05 kurahaupo joined 09:47 notable6 joined
Geth rakudo/main: 9ccd3c374f | (Elizabeth Mattijsen)++ | src/core.e/Format.pm6
Add Format.AST

Since Format isa Str, it already had an .AST method, but that would try to interpret the format string as Raku code, rather than as a sprintf format. By adding this method, at least any confusion in that area is averted.
... (8 more lines)
09:49 statisfiable6 joined, bisectable6 joined
Geth rakudo/main: 5deb9eedec | (Elizabeth Mattijsen)++ | src/core.e/Formatter.pm6
Streamline Formatter.str-(left|right)-justified

For up to 4% performance improvement and easier inlineability because of smaller bytecode footprint
lizmat %-10s 1M times now 45x as fast as legacy sprintf 11:19
was 43x 11:27
Geth rakudo/main: 2e53c87237 | (Elizabeth Mattijsen)++ | src/core.e/Format.pm6
Make zprintf actually produce correct values

Looks like I forgot to change the calling semantics of zprintf to Formatter. Note: "zprintf" is a temporary invention to be able to use legacy sprintf and new Formatter based logic side-by-side in the same language version.
lizmat %-10s 1M times now 68x as fast as legacy sprintf!
and now onto debugging the nitty gritty corner cases of sprintf 11:53
12:00 reportable6 left 12:01 reportable6 joined 12:27 jgaz left 12:32 jgaz joined 12:38 jgaz left, jgaz joined 13:39 kurahaupo left 13:42 kurahaupo joined 13:47 finanalyst joined 14:21 finanalyst left
kurahaupo lizmat: That's a great improvement! 14:25
[Coke] nice 15:24
[Tux] Rakudo v2023.06-22-g2e53c8723 (v6.d) on MoarVM 2023.06-1-g63af27399
csv-ip5xs0.836 - 0.839
csv-ip5xs-205.777 - 6.001
csv-parser4.201 - 4.268
csv-test-xs-200.384 - 0.455
test6.394 - 6.539
test-t1.340 - 1.394
test-t --race0.958 - 1.007
test-t-2020.691 - 22.105
test-t-20 --race6.411 - 6.671
18:00 reportable6 left 18:02 reportable6 joined
Geth rakudo/lizmat-range-minmax: 0ea9740cdb | (Elizabeth Mattijsen)++ | src/core.c/Range.pm6
Make sub version of min/max/minmax on Ranges consistent

with the method equivalent. Since "min" and "max" are attributes on the Range object, they will *always* reflect the "left" and "right" values in the Range (even for Ranges such as (10..-10).
There were no sub versions of min/max/minmax for Ranges, so they ... (5 more lines)
rakudo: lizmat++ created pull request #5300:
Make sub version of min/max/minmax on Ranges consistent
18:26 sena_kun joined
Geth rakudo/lizmat-rakuast-pointy: eac7313a80 | (Elizabeth Mattijsen)++ | src/Raku/Grammar.nqp
RakuAST: allow → ↔ as unicode version of -> <->

As discussed on github.com/rakudo/rakudo/wiki/save...from-ASCII
rakudo: lizmat++ created pull request #5301:
RakuAST: allow → ↔ as unicode version of -> <->
rakudo/lizmat-rakuast-fatarrow: 12eba1fd86 | (Elizabeth Mattijsen)++ | src/Raku/Grammar.nqp
RakuAST: allow ⇒ as the unicode version of =>

As discussed on github.com/rakudo/rakudo/wiki/save...from-ASCII
rakudo: lizmat++ created pull request #5302:
RakuAST: allow ⇒ as the unicode version of =>
japhb lizmat: Just read through save-me-from-ASCII. Some (many, actually) don't make a lot of sense to me ... but oddly one of the ones that was already implemented and retracted I think I have a better use for. 19:59
In one of my research projects, I'm using ¿ as a prefix operator for strings to indicate that they are translatable in the context of UI elements and such, like: `my $hint = ¿'Select your preferred visual theme.';` where $hint now contains a TranslatableString object that Does The Right Thing when output into the UI. 20:03
I'm thinking of making (a slightly more advanced form of) it part of Terminal::Widgets, so that basic translateable string marking is always available out of the box. 20:04
s/marking/handling/ 20:05
22:08 sena_kun left 23:17 kurahaupo left