[00:02] *** guifa joined
[00:03] <ugexe> the core keys tests don't expect $?FILE to be a lexical in the stash. it wasn't in the legacy grammar. apparently it was made so to make it easier to read by the moarvm debugger. so im not really sure what to do about that

[00:04] <ugexe> s/made so/made so in rakuast after-the-fact/

[00:08] <ugexe> in other words https://github.com/rakudo/rakudo/commit/313dfb7df0fd makes it so when t/02-rakudo/04-settingkeys-6c.t (among other tests) are run with RAKUDO_RAKUAST=1 they fail

[00:08] <ugexe> presumably we can just change the test or something, but technically that is a regression

[00:11] <ugexe> that being said, https://github.com/rakudo/rakudo/pull/6158 fixes all the other failures in those same tests besides the !INIT_VALUE one (which *is* expected on the legacy frontend but we aren't emitting on rakuast)

[00:12] <ugexe> but that too might suggest changing the test if we decide we don't want it to be expected

[00:55] *** sibl joined
[01:08] *** hulk joined
[01:08] *** kylese left
[01:32] *** kjp left
[01:35] *** kjp joined
[02:15] *** hulk left
[02:15] *** kylese joined
[02:51] *** sibl left
[02:56] *** sibl joined
[03:23] *** vasko4535586 left
[03:29] *** sibl left
[03:33] *** sibl joined
[04:20] *** Aedil joined
[05:21] <disbot2> <melezhik.> Deepseek take on generating Sparrow task check DSL - https://chat.deepseek.com/share/lqq7dkdeuipfbbdwvs - very good and accurate results !

[05:25] <disbot2> <melezhik.> Comparison with Python . https://chat.deepseek.com/share/9hd1n02djgxx7zt6m8

[05:26] <disbot2> <melezhik.> IMHO sparrow is a winner

[05:32] <disbot2> <melezhik.> Parsing logrotate configuration- https://chat.deepseek.com/share/pvy11s328tkgts80hz , also very accurate

[05:41] <disbot2> <melezhik.> Comparison with Python - https://chat.deepseek.com/share/629x5g1r3u6hwb4z9m

[05:42] <disbot2> <melezhik.> Ok. I have done Qwen, chat gpt, Gemini and deepseek, the last one looks like most accurate and without hallucinations.,

[05:44] <disbot2> <melezhik.> All comparison analysis says something like that - “in favor of Sparrow if” :  Choose Task Check DSL when:  Working within existing Sparrow6 infrastructure Need quick, declarative configuration checks Team includes non-programmers who can read DSL syntax Want built-in test reporting without custom formatting code

[05:45] <disbot2> <melezhik.> And always it takes far more line of code when doing the same Python as well as time of adding new rule/check is way more if write in Python

[05:48] <disbot2> <melezhik.> @librasteve feel free to adjust those fundings and refine them upon your discretion

[05:55] *** sibl left
[05:57] *** abraxxa joined
[05:58] *** sibl joined
[06:03] *** abraxxa left
[06:03] *** abraxxa joined
[06:25] *** sibl left
[06:26] *** sibl joined
[06:37] *** Sgeo left
[06:38] <patrickb> ugexe: re $?FILE, I'd say we can just change the tests. I don't expect much ecosystem fallout from this.

[07:10] <Voldenet> actually python is almost never the winner when it comes to either code size or performance

[07:11] <Voldenet> for size it'd be probably saner to compare anything to raku or perl

[07:15] <Voldenet> and for performance no idea