🦋 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.
Xliff \o 01:18
Getting this when trying to compile the rakuast branch: make: *** No rule to make target 'src/core.e/Rakudo/Internals/Sprintf.pm6', needed by 'blib/CORE.e.setting.moarvm'. Stop.
Has anyone encountered this?
lizmat .tell Xliff did you re-run the configuration ? 09:44
tellable6 lizmat, I'll pass your message to Xliff
Geth rakudo: Kaiepi++ created pull request #5062:
Better cope with laziness in list constructors
12:38
bartolin_ lizmat: I'm still trying to figure out what goes wrong with github.com/rakudo/rakudo/issues/5037. Do you maybe have an idea about it? What I don't understand is, which candidate for method "pairs" should be choosen if there are to fitting candidates with the same signature: 14:24
one for the role shapedintarray: github.com/rakudo/rakudo/blob/d059....pm6#L2998
and one for the role shaped1intarray: github.com/rakudo/rakudo/blob/d059...3135-L3143
And it looks to me as if a shaped int array with one dimension has both roles: 14:25
m: say array[int].new(:shape(1)).^roles
camelia ((shaped1intarray) (shapedintarray) (shapedarray) (ShapedArrayCommon) (array::intarray[int]) (Positional[int]) (Positional) (Iterable))
bartolin_ *two fitting candidates (in my first post)