🦋 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.
[Coke] github.com/jonathanstowe/URI-Template/issues/3 - looks like something a blin run would have caught. 01:25
ah. here is the channel that discussed the URI error.
I opened a ticket for someone to close about it. :) 01:26
I noted the version I was using if someone needs a bisect point. 01:38
also, I got the URL for the wrong repo. Use japhb's ticket: github.com/raku-community-modules/URI/issues/48 02:09
[Tux] Rakudo v2021.10-47-gab02205ed (v6.d) on MoarVM 2021.10-26-g770e82e48
csv-ip5xs1.362 - 1.373
csv-ip5xs-2015.351 - 15.898
csv-parser3.813 - 3.958
csv-test-xs-200.373 - 0.373
test6.813 - 7.018
test-t1.545 - 1.575
test-t --race0.969 - 0.994
test-t-2022.666 - 22.892
test-t-20 --race7.422 - 7.764
 07:42
Kaiepi isn't there an issue wrt inferring list element types in signatures somewhere? 08:07
the .all ~~ ... idiom isn't so hot for lists in particular, but idk if why that is has already been brought up there
lizmat Files=1349, Tests=117859, 309 wallclock secs (34.93 usr 9.29 sys + 4264.78 cusr 364.97 csys = 4673.97 CPU) 09:00
Geth rakudo: ce0d31fb91 | (Elizabeth Mattijsen)++ | src/core.c/IO/Path.pm6
Make sure IO::Path.slurp returns failures

Fixes #4619		 09:32
nine Huh...trying to teach our developers at work I'm surprisded to find that exception handling and especially failures are not as well documented as needed. E.g. I cannot find any mention at all that CATCH sets $_ to the exception object. Some of the examples demonstrate this but only indirectly by using shorthand notation for calling methods on $_ 10:23
Failures are not mentioned at all in the exception topic and are documented only in docs.raku.org/type/Failure and that's a very technical and dense description that even I need to concentrate hard to follow. 10:24
Neither the docs on Exception, nor on Failure link to docs.raku.org/language/exceptions 10:25
lizmat github.com/Raku/doc/issues/new/choose ? 10:26
Geth rakudo/DEPRECATE-smartmatch-on-Junction: 8036bf782c | (Elizabeth Mattijsen)++ | src/core.c/Mu.pm6
DEPRECATE smartmatching on Junctions

In response to github.com/Raku/problem-solving/issues/297 this commit DEPRECATEs the use of Junctions on the left hand-side of a smart match, and as an argument to .ACCEPTS. Dis-allowing of a smart match, and as an argument to .ACCEPTS. Dis-allowing this feature has quite a bit of spectest fallout, so this will need to be looked at more carefully in the future.		 10:44
rakudo: lizmat++ created pull request #4620:
DEPRECATE smartmatching on Junctions
gfldex m: my $a = 42; say $a.not-there(); CATCH { when X::Method::NotFound { .resume } } 11:22
camelia Already set resume init args for this dispatcher
in block <unit> at <tmp> line 1
gfldex Is this a newdisp regression?
timo committable6: 2021.04 my $a = 42; say $a.not-there(); CATCH { when X::Method::NotFound { .resume } } 11:23
committable6 timo, ¦2021.04: «Method 'not-there' not found for invocant of class 'Int'␤ in block <unit> at /tmp/L8xUi07Xoe line 1␤␤ «exit code = 1»»
gfldex pre newdisp the error was: "Cannot find method 'gist' on 'BOOTException': no method cache and no .^find_method in block <unit> at - line 1 11:26
.resume is of limited use here anyway, because it doesn't take a "return"-value. 11:27
Should I let jnthn know? 11:34
lizmat yeah, perhaps mention it on #moarvm 11:47
Geth ¦ rakudo: jnthn self-assigned A LEAVE in nested scope in a sub can cause loss of the return value github.com/rakudo/rakudo/issues/4521 12:01
sena_kun m: Rat(Inf).say; 12:06
camelia Attempt to divide by zero when coercing Rational to Str
in block <unit> at <tmp> line 1
Geth nqp: 84fa661070 | (Elizabeth Mattijsen)++ | tools/templates/MOAR_REVISION
Bump NQP to get the latest MoarVM fixes
 14:38
rakudo: b258de0bf4 | (Elizabeth Mattijsen)++ | tools/templates/NQP_REVISION
Bump Rakudo to get the latest MoarVM fixes
 14:55
Geth rakudo: e98e17da7d | (Elizabeth Mattijsen)++ | 3 files
Make sure ParallelSequence is included in shas
 15:41
lizmat m: dd "foo bar".match: / b <( / 20:26
camelia Match.new(:orig("foo bar"), :from(5), :pos(5))
lizmat I wonder whether there's a reason for <( as the last token, to not take the rest of the string
m: dd "foo bar".match: / )> b /
camelia Match.new(:orig("foo bar"), :from(4), :pos(5))
lizmat m: say "foo bar".match: / )> b / 20:27
camelia ｢｣
lizmat same for that one: why note take all from the start of the string ?
*not 20:29

Powered by Cro and the Raku® Programming Language.

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

Thank you!