🦋 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.
Geth rakudo: vrurg++ created pull request #4491:
Make Scalar a non-value-object		 02:23
roast: vrurg++ created pull request #753:
Use more correct approach in list EVAL roundtrip		 02:37
[Tux] Rakudo v2021.07-16-g10b016ccf (v6.d) on MoarVM 2021.07-10-g96ce6d848
csv-ip5xs0.837 - 0.852
csv-ip5xs-209.023 - 9.248
csv-parser26.779 - 29.015
csv-test-xs-200.372 - 0.382
test7.718 - 8.287
test-t1.974 - 1.995
test-t --race0.982 - 0.996
test-t-2033.055 - 33.382
test-t-20 --race10.493 - 10.648
 06:47
Geth rakudo: 56fce9e796 | (Vadim Belman)++ | src/core.c/Scalar.pm6
Make Scalar a non-value-object

Which it is not.
Resolves Raku/problem-solving#291		 08:43
rakudo: 16917ac4d3 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/Scalar.pm6
Merge pull request #4491 from vrurg/problem-solving-291

Make Scalar a non-value-object
roast: 2b341391d9 | (Vadim Belman)++ | S02-types/list.t
Use more correct approach in list EVAL roundtrip

The previous version of the test expected the same container to be preserved for an itemized list despite roundtripping it through EVAL. But this is incorrect because:
  - we itemize two different lists despite both being empty
... (11 more lines)		 08:44
roast: ce59cd9c9c | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | S02-types/list.t
Merge pull request #753 from vrurg/problem-solving-291

Use more correct approach in list EVAL roundtrip
Xliff \o 16:22
if you have a proto sub, can it perform operations before calling candidates?
If so, how? I've tried using '*' and 'nextsame' but they don't work. 16:23
ugexe m: proto sub foo(|) { say 42; {*}; say 420; }; multi sub foo($a) { say $a }; foo(666) 16:27
camelia 42
666
420
Xliff So it's "{*} and not just *" 16:39
heh
*headdesk*
[Coke] Aye. I imagine it would be confused with a Whatevercode otherwise. 16:44
Xliff m: proto sub foo(|) { say 42; {*}; say 420; }; multi sub foo($a) { say $a }; foo(666) 20:04
camelia 42
666
420
Xliff m: proto sub foo(|) { say 42; { * }; say 420; }; multi sub foo($a) { say $a }; foo(666)
camelia 42
420
Xliff Um. Isn't that a bit LTA?
"{*}" works, but "{ * }" doesn't? 20:05
MasterDuke58 {*} is a special thing, but yeah, a bit LTA 20:07
Xliff Would be nice to make that \s insensitive, y'know? 20:48
MasterDuke58 token onlystar is, but token sym:<onlystar> is just the '{*}' 20:50
github.com/rakudo/rakudo/blob/mast...3237-L3240 20:51
b2gills I used {*} in my `bytes.p6` byte counting program gist.github.com/b2gills/93d1e2aa6583b95315b2 21:04
It made it so all of the counting happened in the MAIN proto. The rest of the multis of MAIN just returned a byte array or similar.

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!