#raku-dev on 14 September 2023 - 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.

00:00 reportable6 left 00:02 reportable6 joined 00:42 leont left, leont joined 01:23 Geth left 02:23 benchable6 left, quotable6 left, squashable6 left, tellable6 left, committable6 left, sourceable6 left, unicodable6 left, notable6 left, nativecallable6 left, releasable6 left, greppable6 left, statisfiable6 left, bisectable6 left, linkable6 left, evalable6 left, bloatable6 left, coverable6 left, shareable6 left, reportable6 left, notable6 joined, nativecallable6 joined, tellable6 joined 02:24 shareable6 joined, linkable6 joined, unicodable6 joined, sourceable6 joined, bisectable6 joined, reportable6 joined, benchable6 joined, greppable6 joined, evalable6 joined, statisfiable6 joined 02:25 coverable6 joined, bloatable6 joined, committable6 joined, squashable6 joined 02:26 quotable6 joined, releasable6 joined 04:36 unicodable6 left, reportable6 left, nativecallable6 left, greppable6 left, sourceable6 left, statisfiable6 left, tellable6 left, committable6 left, evalable6 left, quotable6 left, notable6 left, coverable6 left, bloatable6 left, squashable6 left, releasable6 left, bisectable6 left, linkable6 left, shareable6 left, benchable6 left, bisectable6 joined 04:37 coverable6 joined, notable6 joined, statisfiable6 joined, nativecallable6 joined, tellable6 joined, releasable6 joined, sourceable6 joined, quotable6 joined 04:38 reportable6 joined, bloatable6 joined, benchable6 joined, unicodable6 joined 04:39 committable6 joined, squashable6 joined, evalable6 joined, linkable6 joined, shareable6 joined, greppable6 joined 05:39 nativecallable6 left, coverable6 left, evalable6 left, bloatable6 left, benchable6 left, committable6 left, linkable6 left, notable6 left, shareable6 left, squashable6 left, sourceable6 left, reportable6 left, releasable6 left, tellable6 left, unicodable6 left, greppable6 left, quotable6 left, bisectable6 left, statisfiable6 left 05:40 sourceable6 joined, benchable6 joined, squashable6 joined, bisectable6 joined, linkable6 joined, committable6 joined, unicodable6 joined 05:41 bloatable6 joined, nativecallable6 joined, statisfiable6 joined, evalable6 joined, greppable6 joined, releasable6 joined 05:42 coverable6 joined, quotable6 joined, tellable6 joined, shareable6 joined, notable6 joined, reportable6 joined 06:00 reportable6 left 06:02 reportable6 joined 06:11 jgaz left 06:13 jgaz joined 07:28 rba left, rba_ joined, rba_ is now known as rba 07:47 Geth joined 07:56 Geth left, Geth joined 08:24 finanalyst joined 08:53 squashable6 left 08:54 squashable6 joined 10:29 tellable6 left, notable6 left, squashable6 left, quotable6 left, benchable6 left, shareable6 left, evalable6 left, unicodable6 left, committable6 left, statisfiable6 left, bisectable6 left, coverable6 left, linkable6 left, sourceable6 left, reportable6 left, bloatable6 left, greppable6 left, nativecallable6 left, releasable6 left, quotable6 joined, coverable6 joined 10:30 bloatable6 joined, releasable6 joined, squashable6 joined 10:31 bisectable6 joined, sourceable6 joined, evalable6 joined, committable6 joined, notable6 joined, shareable6 joined, linkable6 joined 10:32 benchable6 joined, greppable6 joined, reportable6 joined, statisfiable6 joined, tellable6 joined, nativecallable6 joined, unicodable6 joined 10:45 guifa left 11:59 finanalyst left 12:00 reportable6 left, reportable6 joined 12:01 tonyo left, tonyo joined

gfldex

m: my &foo = BEGIN 'proto sub foo(|) {*}'.EVAL; multi sub foo($i) { }; foo(42);

13:00

camelia

===SORRY!=== Error while compiling <tmp>
Redeclaration of routine 'foo'. Did you mean to declare a multi-sub?
at <tmp>:1
------> foo(|) {*}'.EVAL; multi sub foo($i) { }⏏; foo(42);
expecting any of:
horizontal whi…

gfldex

m: constant &foo = BEGIN 'proto sub foo(|) {*}'.EVAL; multi sub foo($i) { }; foo(42);

camelia

( no output )

gfldex

m: constant &foo = BEGIN 'proto sub foo(|) { nextwith() }'.EVAL; multi sub foo($i) { }; foo(42);

camelia

nextwith is not in the dynamic scope of a dispatcher
in sub foo at EVAL_0 line 1
in block <unit> at <tmp> line 1

gfldex

Is there any way to make that work?

13:01

This is an urgent question. A blogpost depends on it! :->

lizmat

what should the nextwith dispatch to?

13:02

gfldex

m: constant &foo = BEGIN 'proto sub foo(|) { nextwith(42) }'.EVAL; multi sub foo($i) { }; foo(42);

13:03

camelia

nextwith is not in the dynamic scope of a dispatcher
in sub foo at EVAL_0 line 1
in block <unit> at <tmp> line 1

gfldex

Call the next candidate.

This is golfed and as such makes little sense.

13:04

lizmat

but you're calling it in the proto? That's generally where the buck ends ?

gfldex

ungolfed: gist.github.com/gfldex/10c78c78482...f15326279d

13:05

Then I may not understand proto (what is likely).

lizmat

without optimizations, the proto sub foo is the sub that gets called whenever you do "foo()"

13:07

that will then look at the given args and decide which of its candidates to actually run

(which is basically what {*} does)

13:08

proto foo(|) {*}

is just short for:

gfldex

I want to modify args in the proto before the dispatch continues.

lizmat

proto sub foo(|) { {*} }

samewith ?