[00:03] *** timo left
[00:04] *** timo joined
[02:22] *** Geth joined
[09:26] *** sp1983 joined
[09:35] *** sp1983 left
[11:19] *** finanalyst joined
[12:23] *** spa1983 joined
[12:25] *** spa1983 left
[12:28] *** lizmat_ left
[12:28] *** lizmat joined
[12:52] *** [Tux] left
[12:56] *** [Tux] joined
[13:54] <Geth> ¦ rakudo/lizmat-26: 758ad65aa8 | (Elizabeth Mattijsen)++ | src/Raku/Actions.nqp

[13:54] <Geth> ¦ rakudo/lizmat-26: RakuAST: fix typos in error handling

[13:54] <Geth> ¦ rakudo/lizmat-26: review: https://github.com/rakudo/rakudo/commit/758ad65aa8

[13:56] <lizmat> ugexe: the tests are actually in the "if" module  :-)

[13:56] <lizmat> as to syntax:    yes, I think it would be nice to be able to say something like:

[13:57] <lizmat> use $condition ?? Foo !! Bar

[13:57] <lizmat> and: use

[13:57] <lizmat> use Foo if $condition;

[13:57] <lizmat> use Bar unless $condition

[13:58] <lizmat> but we have the "if" module pretty upstream not working under RakuAST

[13:59] <lizmat> and fixing this in  module land has so far not worked out other than maybe creating a slang, which felt wrong

[13:59] <lizmat> afk&

[14:53] *** sp1983 joined
[14:59] *** sp1983 left
[15:15] *** sp1983 joined
[15:36] *** sp1983 left
[17:17] <ugexe> Yeah but I think for a 10+ year old module that is not used at all or hardly used it isn’t a big deal to not support it. Certainly it shouldn’t dictate what the core syntax would be 

[17:18] <ugexe> The right syntax is important because it should also work for need, require, etc. and it doesn’t really need to be humanized either 

[17:19] <ugexe> Huffmanized rather 

[17:24] <ugexe> It’s quite out of place as an adverb as well as it has nothing to do with an identity 

[17:24] <lizmat> well, yes

[17:25] <lizmat> "10+ year old module"  true

[17:25] <lizmat> "is not used at all or hardly" untrue, its failure e.g. breaks Crypt::Random, which in turn breaks 9 other distribution, amongst which is Cro

[17:27] <lizmat> and then, who knows what's out there on DarkPan

[17:28] <ugexe> I will write up my thoughts on why it’s wrong when I get back. If we follow this pattern then the core is going to get bloated with not well thought out syntax 

[17:33] <lizmat> fair enough   meantime I'm going to keep looking in fixing the module for RakuAST, so at least we won't need people to change their code

[17:34] <Geth> ¦ rakudo/main: d9166ef4cf | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/Raku/Actions.nqp

[17:34] <Geth> ¦ rakudo/main: RakuAST: streamline module loading action a bit

[17:34] <Geth> ¦ rakudo/main: 

[17:34] <Geth> ¦ rakudo/main: DRYer and hopefully better readable

[17:34] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/d9166ef4cf

[18:40] <Geth> ¦ rakudo/lizmat-27: 86bb5fdfad | (Elizabeth Mattijsen)++ | src/Raku/Actions.nqp

[18:40] <Geth> ¦ rakudo/lizmat-27: RakuAST: make sure all expressions are handled

[18:40] <Geth> ¦ rakudo/lizmat-27: 

[18:40] <Geth> ¦ rakudo/lizmat-27: By using the magic RakuAST::BeginTime.IMPL-BEGIN-TIME-EVALUATE

[18:40] <Geth> ¦ rakudo/lizmat-27: method.  Which should probably need to be abstracted into a

[18:40] <Geth> ¦ rakudo/lizmat-27: method "execute" on RakuAST::Node.

[18:40] <Geth> ¦ rakudo/lizmat-27: review: https://github.com/rakudo/rakudo/commit/86bb5fdfad

[20:20] *** JRaspass left
[20:20] *** JRaspass joined
[22:07] *** timo left
[22:08] *** timo joined
[22:24] *** finanalyst left
[22:31] *** finanalyst joined
[22:47] *** finanalyst left