🦋 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:03 reportable6 joined 03:03 linkable6 left, bloatable6 left, squashable6 left, tellable6 left, nativecallable6 left, notable6 left, unicodable6 left, quotable6 left, evalable6 left, coverable6 left, greppable6 left, benchable6 left, sourceable6 left, releasable6 left, statisfiable6 left, committable6 left, bisectable6 left, shareable6 left, reportable6 left, greppable6 joined, statisfiable6 joined, nativecallable6 joined 03:04 unicodable6 joined, benchable6 joined, coverable6 joined, releasable6 joined, bisectable6 joined, frost25 joined 03:05 squashable6 joined, sourceable6 joined, bloatable6 joined, shareable6 joined, reportable6 joined, quotable6 joined 03:06 linkable6 joined, frost25 left, frost25 joined, frost25 is now known as frost, notable6 joined, committable6 joined, tellable6 joined, evalable6 joined 03:40 frost left 04:40 committable6 left, statisfiable6 left, quotable6 left, sourceable6 left, bisectable6 left, evalable6 left, benchable6 left, squashable6 left, releasable6 left, tellable6 left, nativecallable6 left, bloatable6 left, greppable6 left, reportable6 left, notable6 left, linkable6 left, coverable6 left, unicodable6 left, shareable6 left 04:41 reportable6 joined, benchable6 joined, committable6 joined, evalable6 joined, bisectable6 joined 04:42 tellable6 joined, sourceable6 joined, bloatable6 joined, squashable6 joined, coverable6 joined, statisfiable6 joined 04:43 linkable6 joined, releasable6 joined, notable6 joined, nativecallable6 joined, unicodable6 joined, shareable6 joined, greppable6 joined 04:44 quotable6 joined 06:00 reportable6 left 06:02 reportable6 joined 06:16 sena_kun joined
[Tux] Rakudo v2023.06-191-ge4b4bdeb5 (v6.d) on MoarVM 2023.06-4-g75fe055c2
csv-ip5xs0.816 - 0.852
csv-ip5xs-205.117 - 5.532
csv-parser4.138 - 4.738
csv-test-xs-200.341 - 0.350
test5.971 - 6.933
test-t1.289 - 1.399
test-t --race0.850 - 0.950
test-t-2020.885 - 21.498
test-t-20 --race5.909 - 6.291
06:47
08-05 17:24:58 ← I forgot to post, but Wendy noted the nice score 06:48
5 2022-08-15 19:32:17 test-t 1.335
4 2022-07-23 11:27:47 test-t 1.335
3 2022-10-31 18:23:22 test-t 1.332
2 2022-06-21 18:33:38 test-t 1.332
1 2023-08-05 17:35:40 test-t 1.289
06:52 sena_kun left 10:54 reportable6 left, bisectable6 left, unicodable6 left, tellable6 left, linkable6 left, committable6 left, squashable6 left, greppable6 left, quotable6 left, releasable6 left, notable6 left, benchable6 left, sourceable6 left, nativecallable6 left, statisfiable6 left, bloatable6 left, shareable6 left, evalable6 left, coverable6 left, evalable6 joined, sourceable6 joined, committable6 joined, tellable6 joined 10:55 shareable6 joined, benchable6 joined, bloatable6 joined, coverable6 joined, statisfiable6 joined 10:56 reportable6 joined, unicodable6 joined, squashable6 joined, notable6 joined, quotable6 joined, releasable6 joined, nativecallable6 joined, linkable6 joined, greppable6 joined 10:57 bisectable6 joined 11:20 ab5tract left
lizmat notable6: weekly 11:42
notable6 lizmat, 1 note: 2023-08-01T07:44:29Z <lizmat>: dev.to/finanalyst/rakudoc-revision...mment-4hjb
lizmat notable6: weekly reset
notable6 lizmat, Moved existing notes to “weekly_2023-08-07T11:42:29Z”
12:00 reportable6 left 12:01 reportable6 joined 12:02 ab5tract joined 12:16 ab5tract left
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2023/08/07/2023-...doc-gamma/ 12:17
bisectable6: sub a() { dd CALLER::LEXICAL::<$a> }; my $a = 42; a 12:25
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, ¦6c (68 commits): «Int $a = 42␤» 12:26
lizmat, Nothing to bisect!
lizmat meh
14:50 Xliff joined
Xliff Raku-GLib suite timing statistics for Raku 2023.06.194.ga.4.a.2.bbd.24.e 14:50
Using the following processor: AMD Ryzen 9 5950X 16-Core Processor
Total number of projects: 34 (506509 loc)
Total non-parallel compile times: 11094.810 (326.318 avg)
Total parallel compile times: 2341.308 (68.862 avg) 4.739x speedup
lizmat starts to wonder whether custom infixes really do need a slang, or that there could be a smarter way in RakuAST 17:52
18:00 reportable6 left 18:03 reportable6 joined
nemokosch do "custom infixes" need a slang currently? 18:03
lizmat internally they do, yes 18:08
which is e.g. why they don't work in the REPL
nine We mix into the grammar. Not sure that already constitutes a slang. 18:11
lizmat ok, well, it's lexical, so for all practical purposes it could be considered a slang, no ? 18:17
nine Even if, what's the consequence? 18:21
I.e. I see nothing wrong with that :)
lizmat mixing something into the grammar is a very CPU intensive and memory bloating operation
whereas when we encounter something in an infix position, we just need to make sure there's something valid there 18:22
and that lookup could be just a hash hanging off off $?LANG
I mean, from a QAST point of view, custom infixes are generated the same was as built-in infixes, are they not ? 18:23
Xliff I thought custom operators was just syntax sugar for infix:<$op>($lhs, $rhs)
lizmat the grammar also needs to be able to understand the op
to be able to parse code that uses that custom infix 18:24
nemokosch makes sense 18:30
lizmat m: dd $*KERNEL.bits 18:38
camelia 64
lizmat looks like that's 32 on the M1
while more than 32 bits are definitely supported 18:40
[Coke] m: dd $*KERNEL 18:43
camelia Kernel linux = Kernel.new(release => Str, hardware => Str, arch => Str, bits => Int, name => "linux", auth => "unknown", version => Version, signature => Blob, desc => Str)
[Coke] ^^ that's LTA.
(we get types instead of the values)
lizmat yeah, and then if you ask for bits, it does
$.hardware ~~ m/ _64 | w | amd64 / ?? 64 !! 32)
arm64 missing in this picture 18:44
this breaks P5pack :-)
Geth rakudo/main: 5d4bb333d1 | (Elizabeth Mattijsen)++ | src/core.c/Kernel.pm6
Make $*KERNEL.bits correct on ARM64 processors

Aka Apple's M1/M2
18:52
[Coke] nice. 18:56
what's w. Wide?
lizmat I haz no idea 19:00
nine "naive approach" indeed 19:05
[Tux] Rakudo v2023.06-194-ga4a2bbd24 (v6.d) on MoarVM 2023.06-4-g75fe055c2
csv-ip5xs0.810 - 0.842
csv-ip5xs-205.142 - 5.783
csv-parser3.563 - 3.628
csv-test-xs-200.344 - 0.386
test6.750 - 7.499
test-t1.437 - 1.547
test-t --race0.810 - 0.922
test-t-2019.727 - 20.636
test-t-20 --race6.687 - 6.785
19:06
lizmat just updated all of the P5 modules that where relying on $_ being dynamic 19:11
so that $_ no longer needs to be dynamic, so we can make $_ a local with all of its efficiency improvement
coleman Wow awesome 19:13
lizmat m: sub a() { dd CALLER::LEXICAL::<$a> }; my $a = 42; a # the secret 19:14
camelia Int $a = 42
coleman what is "dd" in this context? I don't know much about the internals. 19:15
lizmat dd is the tiny data dumper, so tiny it lost the "t" 19:16
it's basically: note $foo.raku on steroids
20:27 ab5tract joined
Xliff Is there something in the ecosystem that does Positional and Associative at the same time? 20:52
nemokosch isn't Match something like that itself? 21:14
guifa_ I think Match and Captures both do. 21:18
Xliff: are you wanting something that tracks the order of entries (I think there's an OrderedHash for that) or one that acts like JS object that tracks the positional and named independently? 21:19
Xliff Actually, I want a object that behaves like both a Hash and an Array. 21:57
So I wrote my own that wraps both. :) 21:58
22:25 Xliff left 23:19 kjp left 23:22 kjp joined