#raku-dev on 29 May 2024 - Raku Programming Language Log

🦋 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.

jdv

ab5tract: insanity

02:41

releasable6

Next release in ≈1 day and ≈15 hours. 1 blocker. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft

03:00

06:20 [Tux] joined 07:29 [Tux] left 07:32 [Tux] joined 07:45 sena_kun joined 08:00 finanalyst joined 09:28 sena_kun left 09:33 sena_kun joined 10:57 lizmat_ joined 10:59 Geth left, Geth joined, sena_kun left 11:01 lizmat left, lizmat_ left, sena_kun joined, lizmat joined

[Tux]

Rakudo v2024.04-136-g45966a8cd (v6.d) on MoarVM 2024.04-10-gd67da80f3

csv-ip5xs	0.260	-	0.261
csv-ip5xs-20	1.130	-	1.172
csv-parser	1.603	-	1.607
csv-test-xs-20	0.141	-	0.141
test	1.999	-	2.027
test-t	0.425	-	0.430
test-t --race	0.270	-	0.277
test-t-20	5.138	-	5.204
test-t-20 --race	1.230	-	1.231

11:13

tux.nl/Talks/CSV6/speed4-20.html / tux.nl/Talks/CSV6/speed4.html tux.nl/Talks/CSV6/speed.log

lizmat

weird find of the day:

13:48

my $s = (1,2,3); dd $s.values.values.values.values.values

evalable6

(1, 2, 3).Seq

lizmat

my $s = (1,2,3); dd $s.values.values.values.values.values.values

evalable6

(1, 2, 3)

lizmat

List.values changes to a Seq (and is documented as such)

Seq.values changes to a List

and is not documented

13:50

feels to me Seq.value should return the invocant, to remain consistent ?

*values

13:53 nine left 13:54 nine joined

lizmat

sadly we have a test that checks for Seq.values being a Positional :-(

13:58

however, I find that test rather suspicious

14:00

anyways, for post 2024.05

14:02

afk&

14:04

14:47 jdv left 14:48 jdv joined

Geth

rakudo/main: 042660d8dc | (Elizabeth Mattijsen)++ | src/core.c/RakuAST/Fixups.rakumod
RakuAST: handle =numdefn the same as =defn

16:04

rakudo/main: b7116755eb | (Elizabeth Mattijsen)++ | src/core.c/RakuAST/Fixups.rakumod
RakuAST: fix issues with new "procedural" table

These tables have =cell, =row, =column and =comment blocks in them and are thus *not* defined by pure text layout and are now produced as ::Doc::Blocks with types "cell", "row" etc. basically without any meddling.
Also introduce Doc::Block.procedural method, which returns True if the Doc::Block is this new type of table. Else it returns False

18:20

rakudo/main: 851aa49030 | ab5tract++ | t/12-rakuast/xx-fixed-in-rakuast.rakutest
Add test case for parenthesized prime in where clause

It should not produce a 'useless use' worry.
It should arguably produce a 'probably not what you meant' worry instead, but that's for a different discussion.
R#1525 (#1525)

19:01

linkable6

R#1525 [open]: github.com/rakudo/rakudo/issues/1525 [useless warnings][Fixed in RakuAST] Useless useless when parens used around whatevercode in where

ab5tract

m: class C { method Slip { "doing my thing" } }; dd |C.new

19:07

camelia

C.new

ab5tract

how did I get the impression that `|` was just a prefix-y way of calling the Slip coercer on an object? :S

lizmat

| was originally designed to be only usable for flatteninng / deflattening in signatures

19:08

that was before Slip was a thing (which only came into being during the GLR)

19:09

ab5tract

right, I only remember coming to know of both `|` and `Slip` during/after the GLR

maybe that's how they came to be associated in my mind...

19:10

with just few demonstrations in my terminal, it's quite clear that they do significantly different things :)

19:14

regardless, R#1966 raises an interesting question imo

19:15

linkable6

R#1966 [open]: github.com/rakudo/rakudo/issues/1966 [RFC] Ability to specify how an object flattens in signatures

19:38 finanalyst left 19:41 finanalyst joined 20:08 sena_kun left 20:15 finanalyst left, finanalyst joined 21:15 finanalyst left

gfldex

m: sub a(*%h) { dd %h; }; class Foo does Associative { method AT-KEY(|) { 42} }; my %h := Foo.new; a %h;

21:26

camelia

===SORRY!=== Error while compiling <tmp>
Calling a(Associative) will never work with declared signature (*%h)
at <tmp>:1
------> od AT-KEY(|) { 42} }; my %h := Foo.new; ⏏a %h;

gfldex

m: sub a(*%h) { dd %h; }; class Foo does Associative { method AT-KEY(|) { 42} }; my %h := Foo.new; a(|%h);

21:28

camelia

Too many positionals passed; expected 0 arguments but got 1
in sub a at <tmp> line 1
in block <unit> at <tmp> line 1

gfldex

ab5tract: I updated the example and error message and provided my 2 constant h = Foo.new;