Geth rakudo: ugexe++ created pull request #6506:
RakuAST: extend lexical lowering to anonymous variables and BEGIN-compiled routines
01:23
[Coke] (this hopefully will also let me do some more work on blin itself since I'm not going to have worry about leaving the box turned on) 02:51
... this seems faster. 02:55
I have half as much memory, but 4 times the cores as the other box.
gist.github.com/coke/f78decdb75da5...b66731e9db - there's the first blin run on this machine (no new failures yet on main) 03:55
04:55 Pixi` joined, ShimmerFairy left 04:56 ShimmerFairy joined 04:58 Pixi left 04:59 Pixi joined 05:00 Pixi` left
ab5tract Hash.prepend doesn’t make sense to me 09:13
It’s not ordered, so how would you prepend?
Hash.append seems to be broken: 09:17
m: my %h; dd %h.append: :test(66); dd %h
camelia {}
{}
lizmat you need to specify the key *and* one or more values 09:18
also: :test(66) is a named arg to append, that will just get eaten
ab5tract I did specify a key and a value 09:19
And I still hate %_
m: my %h; dd %h.append: %( :test(66) ); dd %h
camelia {:test(66)}
{:test(66)}
ab5tract If it isn’t ordered, append should be the same as push which should be the same as unhurt 09:20
*unshift
If they aren’t the same, what on earth are they actually doing differently? 09:21
Do any of these methods actually take a named argument?
lizmat nope 09:22
m: my %h; %h.push("a",42); dd %h; %h.push("a",666); dd %h 09:23
camelia {:a(42)}
{:a($[42, 666])}
ab5tract Then surely it would be better for them to take *%_ as a list of keys and values and not as a (nonexistent) named argument
lizmat you're misunderstanding what Hash.push/append do
m: my %h; %h.push("a",42); dd %h; %h.push("a",[666,777]); dd %h
camelia {:a(42)}
{:a($[42, [666, 777]])}
lizmat m: my %h; %h.push("a",42); dd %h; %h.append("a",[666,777]); dd %h 09:24
camelia {:a(42)}
{:a($[42, 666, 777])}
ab5tract ah, right your are
ab5tract scrambles for a hole in the rocks
09:28 finanalyst joined
ab5tract lizmat: after that embarrassing demonstration of my lack of recall, I think it makes sense that we would have prepend and unshift as well 09:42
lizmat well, in the past 14 years of doing raku, yesterday was the first day I could have used it 09:43
so it's definitely not a big thing
but for consistency's sake, it feels like an omission not to have Hash.unshift/prepnd 09:44
*prepend
ab5tract Indeed, it feels like an oversight 09:54
Geth rakudo/lizmat-30: 6f266b9cdd | (Elizabeth Mattijsen)++ | src/Raku/Actions.nqp
RakuAST: worry about unknown use adverbs in 6.e+

As a result of discussion about 'use' adverbs in
   github.com/Raku/problem-solving/issues/525
   use Test:foo:ver:bar; ok 1; # no worries
   use v6.e.PREVIEW; use Test:foo:ver:bar; ok 1;
   Potential difficulties:
   Detected unsupported adverbs in 'use' statement: :foo:bar
10:32
rakudo: lizmat++ created pull request #6508:
RakuAST: worry about unknown use adverbs in 6.e+