🦋 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.
lizmat ok, I was thinking "raku -e 'Foo: ...' 00:20
in any case, it should not be an IO object anyway... 00:21
nine What would it be for artificially created labels (think RakuAST::Label.new) 07:18
lizmat whatever you specify with the creation of it ? 07:42
Files=1351, Tests=117115, 291 wallclock secs (34.99 usr 9.49 sys + 4056.01 cusr 325.05 csys = 4425.54 CPU)
nine Do you have to specify something? 08:02
Currently RakuAST::Label doesn't even have file and line. 08:07
lizmat hmmm... 09:11
could that be a NYI, or something else ? 09:13
in any case, the file and line were exposed in Label.gist and/or Label.Str 09:14
if they were an implementation detail, they shouldn't have been? 09:15
for me, that was the reason for exposing them
nine Are they spec tested? 09:30
gist hasn't been changed since labels got introduced in 2014 09:33
lizmat there are no spectests for Label, apart from it existing as a class 09:47
gfldex There is always nqp::attr. So trying to hide stuff in CORE is largly futile. 10:08
And that there are no spectests is hardly surprising. Nobody considered Label as a tool outside of the scope of the compiler itself. Having anything being an object comes at the price that the user can use them as such. 10:10
lizmat gfldex: so you think I should revert? 10:13
gfldex no
My blogpost will explain. :)
lizmat ok, just checking :-)
ugexe it would seem a bit odd to find that there is not consensus to do this and there being a blog post suggesting it can be done 12:28
i dont have an opinion on the label thing itself, just pointing out the optics of what i just read 12:29
lizmat well, to me the eye opener was of using a Label as just that: a way to label a piece of code, not just for next / last 12:35
m: sub bar($l) { dd $l }; FOO: bar FOO 12:37
camelia Label.new(name => "FOO", file => "<tmp>", line => 1)
Geth XML: vrurg++ created pull request #65:
Extend attribute matching capabilities		 15:18
XML: caa204a486 | (Vadim Belman)++ | 2 files
Prepare for zef echosystem

Added mi6 dist.ini and changed `auth` in META6.		 16:03
XML/main: 4414af2a42 | (Vadim Belman)++ | .github/workflows/main.yml
Primary branch changed to main
 16:05
XML/main: c540e06b1a | (Vadim Belman)++ | 3 files
Extend attribute matching capabilities

Implement full smartmatch semantics for non-boolean and optimize booleans.		 16:08
XML/main: 9db3b6eb8d | (Vadim Belman)++ (committed using GitHub Web editor) | 3 files
Merge pull request #65 from vrurg/style-code-matcher

Extend attribute matching capabilities
XML/main: 018cb16d4c | (Vadim Belman)++ | META6.json
Version bump

Release to zef		 16:11
vrurg .ask lizmat could you, pls, release XML to zef? Or add me to raku-community-modules group. 16:12
tellable6 vrurg, I'll pass your message to lizmat
lizmat vrurg: invitation sent 17:40
tellable6 2022-03-03T16:12:40Z #raku-dev <vrurg> lizmat could you, pls, release XML to zef? Or add me to raku-community-modules group.
lizmat vrurg: did that work out ? 18:11
vrurg lizmat: got it, thank you! 20:02
vrurg Weird, why do I keep getting ""raku-community-modules" does not match the username you last logged in with (vrurg) or a group you belong to" from fez? 21:51
Geth XML/main: 4daa102e48 | (Vadim Belman)++ | Changes
Added Changes file

  `mi6` reasonable requirement		 23:00
XML/main: 96d3212ca9 | (Vadim Belman)++ | Changes
0.3.2
 23:03

Powered by Cro and the Raku® Programming Language.

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

Thank you!