[00:00] *** rba left
[00:00] *** rba joined
[01:42] *** coleman left
[01:42] *** coleman joined
[06:10] *** finanalyst joined
[07:38] *** rnddim joined
[07:39] *** rnddim left
[07:39] *** rnddim joined
[07:40] *** ShimmerFairy left
[07:59] <Geth> ¦ rakudo/lizmat-28: c5f9b1695e | (Elizabeth Mattijsen)++ | 2 files

[07:59] <Geth> ¦ rakudo/lizmat-28: RakuAST: use RakuDoc instead of Pod when appropriate

[07:59] <Geth> ¦ rakudo/lizmat-28: review: https://github.com/rakudo/rakudo/commit/c5f9b1695e

[07:59] *** rnddim left
[07:59] <Geth> ¦ rakudo: lizmat++ created pull request #6499: RakuAST: use RakuDoc instead of Pod when appropriate

[07:59] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6499

[08:00] *** rnddim joined
[08:03] <Geth> ¦ rakudo/main: 4 commits pushed by (Nick Logan)++, (Elizabeth Mattijsen)++

[08:03] <Geth> ¦ rakudo/main: 36f557ea4f | RakuAST: drop the subset-named-parameter missing-default worry

[08:03] <Geth> ¦ rakudo/main: d0185e25a6 | Explain the implicit default in optional parameter bind errors

[08:03] <Geth> ¦ rakudo/main: 00186e6a24 | Merge branch 'main' into ugexe/rakuast-drop-subset-default-worry

[08:03] <Geth> ¦ rakudo/main: f7bfd24cc8 | Merge pull request #6480 from ugexe/ugexe/rakuast-drop-subset-default-worry

[08:03] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/compare/d9166ef4cfd5...f7bfd24cc8fc

[08:38] *** finanalyst left
[08:39] *** finanalyst joined
[08:42] *** finanalyst left
[08:48] *** finanalyst joined
[10:17] <Geth> ¦ rakudo/lizmat-29: dffe95ecbd | (Elizabeth Mattijsen)++ | 2 files

[10:17] <Geth> ¦ rakudo/lizmat-29: Refactor error X::Syntax::InfixInTermPosition

[10:17] <Geth> ¦ rakudo/lizmat-29: 

[10:17] <Geth> ¦ rakudo/lizmat-29: This error is most often called if there is an error in Pod/RakuDoc

[10:17] <Geth> ¦ rakudo/lizmat-29: syntax.  So make those types of cases much more elaborate, and

[10:17] <Geth> ¦ rakudo/lizmat-29: mention the fact that a term was expected as a last option.

[10:17] <Geth> ¦ rakudo/lizmat-29: 

[10:17] <Geth> ¦ rakudo/lizmat-29: So a "=begin FOO" without "=end FOO" will now (in RakUAST) be reported as:

[10:17] <Geth> ¦ rakudo/lizmat-29: <…commit message has 7 more lines…>

[10:17] <Geth> ¦ rakudo/lizmat-29: review: https://github.com/rakudo/rakudo/commit/dffe95ecbd

[10:18] <Geth> ¦ rakudo: lizmat++ created pull request #6500: Refactor error X::Syntax::InfixInTermPosition

[10:18] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6500

[14:56] <timo> I feel like we should be able to give a POD parsing related error instead of backtracking all the way back out of the POD parser and then saying "oh you seem to have an equals sign here that is actually an assignment operator that just went in a spot it wasn't allowed to go"

[14:57] <timo> I've wondered about this a few times already, but never spent enough brain time to come up with an actual proposal

[14:58] <timo> we only ever enter the part of the pod parser that is "problematic" in this way when we're at the start of a line, right? that's the only time you can put a "=begin whatever" or a "=foobar"?

[15:02] <timo> but of course, if a custom prefix:<=> operator or a term or so is defined, that would need to take precedence as well

[15:08] <timo> thankfully you cannot define a `sub prefix:<=>` before using it in the grammar anyway :)

[15:11] <timo> m: say "gimme a newline please"

[15:11] <camelia> rakudo-moar f7bfd24cc: OUTPUT: «gimme a newline please␤»

[15:12] <timo> m: sub term:<=begin>() { say "begun" }; say␤=begin␤;

[15:12] <camelia> rakudo-moar f7bfd24cc: OUTPUT: «===SORRY!=== Error while compiling <tmp>␤=begin must be followed by an identifier; (did you mean "=begin pod"?)␤at <tmp>:2␤------> =begin<HERE><EOL>␤»

[15:13] <timo> m: sub term:<=begin>() { say "begun" }; sub infix:<comment>($a, $b) { say "comment passed $a and $b" }; say␤=begin comment␤"haha"

[15:13] <camelia> rakudo-moar f7bfd24cc: OUTPUT: «begun␤comment passed True and haha␤True␤»

[15:13] <timo> but then

[15:14] <timo> m: sub term:<=begin>() { say "begun" }; sub infix:<comment>($a, $b) { say "comment passed $a and $b" }; say␤=begin comment␤"haha"␤=end comment␤"this is just a normal call to sub say";

[15:14] <camelia> rakudo-moar f7bfd24cc: OUTPUT: «this is just a normal call to sub say␤»

[15:14] <timo> that's somewhere between DIHWIDT and "kinda funky behaviour"

[16:05] <timo> https://github.com/raku-community-modules/OpenSSL/pull/113 do we know why this isn't running its checks?

[16:19] <timo> I reviewed and merged that pull request, upgraded the module's dependency on JSON::Fast, and put the changes in the Changes document

[16:20] <timo> but I don't think I have the login details for zef:raku-community-modules, so I think someone else has to actually run the release process; lizmat? :)

[16:28] <timo> actually I have another change that could maybe go in

[16:34] <timo> but it's not critical, I guess

[16:34] <timo> probably something that really wants many people to test it before we put it into the ecosystem

[17:17] *** SmokeMachine_ joined
[17:17] *** tbrowder__ joined
[17:23] <lizmat> timo: "when we're at the start of a line", nope, you can have any amount of whitespace from the start of the line

[17:23] <timo> oh, that does make sense. not just when you're already inside pod

[17:24] *** tbrowder left
[17:24] *** SmokeMachine left
[17:24] *** SmokeMachine_ is now known as SmokeMachine

[17:24] *** tbrowder__ is now known as tbrowder

[17:25] <lizmat> as far as code parsing is concerned: pod is considered whitespace

[17:30] <lizmat> OpenSSL 0.2.8 on its way to the ecosystem

[17:32] <timo> lizmat++ thanks!

[18:22] *** finanalyst left
[21:13] *** timo left
[21:46] *** timo joined
[22:16] *** MasterDuke joined
[23:03] *** MasterDuke left