🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). This channel is logged for the purpose of keeping a history about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Log inspection is getting closer to beta. If you're a beginner, you can also check out the #raku-beginner channel!
Set by lizmat on 25 August 2021.
frost m: (:5a).WHAT.say 09:12
camelia (Pair)
lizmat And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2022/02/14/2022-...-released/ 15:57
dynamite beautiful 16:46
codesections lizmat++
CIAvash lizmat++ 17:29
lizmat: I don't see my blog posts, should I add them to the weekly bot? 17:30
lizmat CIAvash: yes, that would help! :-) 17:41
sorry that I missed them... :-(
CIAvash no problem, they are mentioned in the Twitter section 17:43
weekly: www.ciavash.name/blog/2022/02/13/T...s-in-raku/
notable6 CIAvash, Noted! (weekly)
CIAvash weekly: www.ciavash.name/blog/2022/02/13/h...tor-in-go/ 17:44
notable6 CIAvash, Noted! (weekly)
lizmat completely missed that that was a blog post :-(
lizmat should look closer :-) 17:50
Geth ecosystem: 8746380462 | (Elizabeth Mattijsen)++ | META.list
Lock the commit of Pythonic::Str

While we're moving it to the zef ecosystem		 18:25
leont Experiencing a weird issue where I can't use a class inside a module if it's called X::Client, but can access it when it's renamed to Y::Xlient 19:01
Er, Y::Client
lizmat m: dd X::Client 19:02
camelia Could not find symbol '&Client' in 'X'
in block <unit> at <tmp> line 1
lizmat m: class X::Client { }; dd X::Client
camelia X::Client
leont Er, can't use a class defined inside the module from outside of the module 19:05
leont I can reproduce it with a Foo.rakumod containing «module Foo { class Y::Client {} }», and then running «raku -I. -e 'use Foo; Foo::X::Client.new'» 19:14
CIAvash m: module M { class X::Client {} }; dd X::Client # hmm 19:23
camelia M::X::Client
leont CIAvash: yea,, inside the module it works fine 19:30
*h
Oh wait, I think I see what you mean 19:31
I guess this is because X:: already exists as a namespace
But I still doubt this is what we want 19:32
bartolin_ leont: there is at least this old open issue that points out some oddities with using core namespaces: github.com/Raku/old-issue-tracker/issues/5815 (I didn't try if all the reported still exist, but at least this still looks strange: 19:33
m: class Foo { role X {}; method z { Foo!z } }
camelia ===SORRY!===
Could not locate compile-time value for symbol Method::NotFound
leont bartolin_: yeah, that sounds like the same issue 19:34
Putting it in a package X { class ... } instead seems to work around the issue, but it's still rather surprising
guifa there are some weird things that can happen with using any namespace that exists 22:49
I got a bug report with DateTime::Timezones where my module conflicted with another one that exported `class DateTime::Parse` 22:50
when mine imported in `class DateTime [is DateTime]`, the DateTime::Parse disappeared
that doesn't happen with non-built ins though: 22:53
m: class Foo::Bar { method foo {'foobar'} }; class Foo { ; }; say Foo::Bar.foo
camelia foobar
MasterDuke i just watched p6steve's fosdem talk. i think that's the first time i've ever seen a grammar with two action classes available, very cool 23:06

Powered by Cro and the Raku® Programming Language.

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

Thank you!