🦋 Welcome to the former MAIN() IRC channel of the Raku Programming Language (raku.org). This channel has moved to Libera (irc.libera.chat #raku)
Set by lizmat on 23 May 2021.
00:02 reportable6 left 00:05 Doc_Holliwood left, reportable6 joined
raydiak at least two of them, actually. good grief we sure scattered that far and wide. good marketing I guess 00:37
codesect` And who would have thought that *freenode* would (effectively) go away. 00:38
ugexe github.com/niner/Inline-Perl5/blob...6.json#L55 00:39
also various meta6.json references
codesect` you know that xkcd about IRC? (m.xkcd.com/1782/) I kind of imagined that the guy in the last panel would still be using freenode 00:40
00:42 ggoebel_ joined 00:45 dogbert17 left, dogbert17 joined 00:46 dogbert17 left, dogbert17 joined
raydiak on p6lanet.org too, which we link to from raku.org. and good point, I didn't even check my own readmes yet, pretty sure it's in at least a few of them 00:46
and en.wikipedia.org/wiki/Raku_(progra..._language) 00:48
grep -ir freenode modules.raku.org/ | wc -l # 24 :P 00:56
01:02 Xliff left 01:12 rbt left, rbt joined
Sgeo I'm still a bit scared of mentioning libera in chat 01:29
on Freenode. Just did irc[dot]libera[dot]chat when someone was asking where we were in the Freenode side
01:34 sono joined
raydiak I haven't seen signs that they're chasing individuals, but if they were searching for something, it's probably just "libera". don't think the [dot] does you a lot of good there 01:34
you sould always just point them to raku.org/community/irc 01:35
01:36 sono left, sono joined 02:16 eof left 02:17 summerisle joined 02:26 guifa left
raydiak also 8 pages of results for github.com/search?q=org%3ARaku+fre...;type=code and 6 pages in github.com/search?q=repo%3ARaku%2F...;type=code 02:31
03:10 summerisle is now known as eof 03:11 juanfra[m] joined 03:28 juanfra[m] left, juanfra[m] joined 03:32 guifa joined, guifa left 04:13 rbt left 04:39 swaggboi left 04:52 swaggboi joined 04:58 Doc_Holliwood joined 05:39 codesect` left 05:43 codesections joined 05:44 bd3i left 06:02 ecocode_ joined, reportable6 left 06:05 reportable6 joined 06:13 rbt joined, Doc_Holliwood left 06:14 hankache joined 06:18 Doc_Holliwood joined 06:23 rbt left, rbt joined, rbt left 07:13 ilogger2 left, ilogger2 joined 07:17 Sgeo left 07:34 rbt joined 07:35 dakkar joined
GreaseMonkey ok i had a go at making a reduced HTML parser using a grammar, i've parked it but it does at least walk the tags 07:36
and it dumps a whitespace-stripped dump of it 07:37
07:38 Doc_Holliwood left 07:39 dolmen joined 08:22 AlexDaniel left 08:33 stoned75 joined 08:39 rbt left, rbt joined 08:49 rbt left 08:50 rbt joined 09:09 patrickb joined
Altreus but not significant whitespace I hope :) 09:16
09:29 stoned75 left 09:31 stoned75 joined 09:45 rbt left 09:56 rbt joined, rbt left 10:06 jast joined 10:22 Xliff joined
Xliff \o 10:22
Good morning.
Altreus o/
Xliff I would like to change the precidence rules for infix:<+>. What would be the best way to accomplish this?
Altreus /o\ 10:23
Xliff Please note. Creating a new operator is not in scope.
It MUST be infix:<+>
lizmat should it be active in a lexical scope ?
Xliff lizmat: Whichever way is easiest.
infix:<+> should be tighter than infix:<*> 10:24
moritz I don't think you can do that in raku 10:25
Xliff moritz: Why not? All of the tools are there. 10:26
Is it because of the way CORE defines these ops?
lizmat you could try it by replacing the infix:<+> candidates with your own, starting with:
proto sub infix:<+>(\a,\b) is tighter(&infix:<*>) {*}
Xliff lizmat: OK, will do. 10:27
Altreus I feel like tighter could easily have been called tigher-than and with profound effect
moritz Xliff: I might be wrong, but my understanding is that defining a new operator implies deriving a new grammar from an existing one, and deriving a grammar always means *adding* something 10:28
10:28 colomon joined
Xliff moritz: OK. I am approaching this from the docs: First docs.raku.org/language/operators#L...precedence 10:29
10:29 Doc_Holliwood joined
Xliff And then docs.raku.org/language/optut 10:29
Nothing here mentions grammars.
Just an FYI 10:30
OK. Still returns result indicating no chaneg. 10:37
10:42 stoned75 left
lizmat Xliff: can you verify that it calls *your* infix:<+> ? 10:43
Xliff Sure thing. 10:44
It does.
B should be 2, not 8 10:45
lizmat agree... so the codegen is not looking at the precedence of the actual infix:<+> in scope :-( 10:46
Xliff Looks like it.
10:46 stoned75 joined
lizmat probably worth an issue, so we can make sure it will work when the RakuAST branch lands 10:47
Xliff OK. Will submit.
lizmat I don't see a shorter-term solution
Xliff I'll take what I can get. Thank you, lizmat++ 10:48
lizmat of course, if you could do a PR that would fix that :-)
dakkar I'm pretty sure this problem is related to the other one we noticed a few days ago on the same topic… 10:53
that precedence/associativity of an operator is picked from the first proto or candidate compiled
(and then the compiler doesn't complain when you provide mis-matched candidates) 10:54
so rakudo compiles the setting, sets prec/assoc of infix:<+>, then ignores every other prec/assoc for it, even for a "new" `proto`
Xliff dakkar: Was an issue raised for that? 10:55
dakkar there's already one 10:56
dakkar greps his logs
Xliff 1237?
Wow. Almost 4 years old. 10:57
dakkar yes, that one
10:59 morayj joined
dakkar I've commented with my suggestion from the other day 11:00
(lunch now) 11:01
11:10 RaycatWhoDat left 11:11 RaycatWhoDat joined 11:12 sono left 11:23 dolmen left 11:28 Doc_Holliwood left 11:48 guifa joined 11:51 ecocode_ left 11:57 summer joined 12:02 reportable6 left 12:05 reportable6 joined 12:08 dolmen joined 12:11 stigo left, stigo joined 12:17 summer is now known as Summer 12:23 Grrrr joined 12:31 rbt joined 12:49 mscha joined
mscha m: my @primes = (^∞).grep(&is-prime); say @primes[^25]; 12:50
camelia (2 3 5 7 11 13 17 19 23 29 31 37 41 43 47 53 59 61 67 71 73 79 83 89 97)
dakkar I like that this "give me a few primes" program is like Raku's "hello world" 😁 12:59
13:04 juanfra[m] left 13:06 hankache left 13:11 juanfra[m] joined 13:12 hankache joined 13:13 juanfra[m] left, juanfra[m] joined 13:15 ggoebel_ left, ggoebel_ joined 13:17 ggoebel_ left, ggoebel_ joined 13:29 bd3i joined 13:35 leah2 left 13:36 leah2 joined 13:41 rbt left, rbt joined 13:48 domm joined 13:49 Doc_Holliwood joined 14:00 guifa left 14:02 charsbar joined 14:03 charsbar left, charsbar joined 14:05 dolmen left 14:08 dolmen joined 14:09 charsbar left, charsbar joined 14:12 frost left 14:19 Sgeo joined 14:23 hankache left 14:24 hankache joined 14:30 dolmen left 14:37 jmerelo joined 14:43 dolmen joined 15:03 colomon left 15:06 ilogger2 left, ilogger2 joined 15:08 Guest4 joined, juanfra[m] left 15:09 juanfra[m] joined, Guest4 left 15:10 Guest52 joined 15:11 Guest52 left 15:12 Doc_Holliwood left 15:14 juanfra left, Guest86 joined 15:15 juanfra__ joined 15:17 Guest86 left 15:27 Maylay joined 15:29 m_athias left 15:36 dolmen left 15:40 dolmen joined 15:42 Maylay left 15:44 Maylay joined 15:53 patrickb left 15:56 suman joined
suman m: say "hello libera" 15:57
camelia hello libera
15:58 juanfra[m] left, juanfra[m] joined, juanfra[m] is now known as juanfra 16:00 ggoebel joined 16:02 juanfra left, juanfra joined 16:03 ggoebel_ left 16:09 lizmat left
juanfra__ the private messages to camelia don't work. it used to work on freenode. 16:17
jast I had to rewrite a fair bit of my bot for #git to support account identification. let me know if it turns out something similar will be necessary for camelia, I might be able to give some pointers 16:22
16:23 lizmat joined 16:26 LizBot joined 16:31 dolmen left, rbt left 16:33 dakkar left 16:55 stoned75 left 16:57 juanfra left 17:01 juanfra joined 17:08 ggoebel left 17:19 suman left 17:32 rbt joined 17:41 bd3i left 17:43 juanfra left 17:44 juanfra joined 17:45 daimon is now known as daemon 17:50 juanfra left 17:51 juanfra joined 17:55 Summer left 17:59 morayj left, lucs joined
lucs It appears that bots don't respond to /msg. 18:01
Is this a known problem?
tadzik someone's just pointed it out 18:02
lucs Aha. I'll go ask in #libera
18:02 reportable6 left
jast it's probably an implementation issue 18:02
I've got a bot running that works fine, but I needed to make adjustments because a feature they relied on didn't exist on libera (libera has the "next generation" version of that feature) 18:03
18:03 ggoebel joined, reportable6 joined 18:10 morayj joined
lucs jast: So it replies to your /msg ? 18:18
jast my bot? yes. 18:19
lucs Hmm...
tonyo what bot are you trying to msg lucs
lucs tonyo: camelia
/msg camelia m: say 2 + 2 No reply 18:20
jast looking at the bot's source I'm not seeing anything suspicious 18:24
18:24 juanfra left
lucs jast: Do you get a response from camelia when you do that? 18:25
jast I don't
18:25 juanfra joined
lucs Right :( 18:25
18:26 juanfra left 18:27 juanfra joined
lucs jast: What's that feature you needed to adjust for? 18:29
jast my bot was depending on the "identify-msg" client capability, which has been supersded by "account-tag"
but I don't see camelia using that
18:29 m_athias joined 18:31 Doc_Holliwood joined 18:43 sono joined
juanfra "NickServ (NickServ@services.libera.chat): camelia is not registered." 18:46
maybe the problem is that camelia is not a registered user
jast shouldn't really matter 18:47
juanfra or maybe camelia is registered but the bot is not login with a password 18:48
lucs I'm getting help from someone in #libera and here's what I understand so far:
Yes, the bot better be registered, else it won't be allowed to talk to users who have +R set.
jast ooh, nasty 18:49
juanfra my user has +R, so that's the problem
jast but also not too hard to fix I guess
lucs And more than registered, it also has to be identified, something like /msg nickserv identify pAsSwOrD or using SASL (see libera.chat site). 18:50
jast the bot already supports identifying with nickserv, someone just needs to make it happen on libera 18:51
juanfra you need to be logged and you user can't have +R 18:52
with -R camelia works
lucs juanfra: Welp, I'd rather keep my +R, just saying :) 18:54
juanfra yes, i know. i was just trying to find where was the problem. 18:55
lucs juanfra: Ah, okay, thanks. 18:56
Who handles the bots around here? 18:58
moritz depepnds on the bot, I thinks 18:59
lucs Yeah, makes sense. 19:01
I'm also told: "if possible sasl external and cert auth is more secure way than plain password" 19:02
So the bot owners may have to tweak things a bit for the bots to work seamlessly.
19:04 juanfra__ left 19:09 jmerelo left 19:20 stoned75 joined 19:25 mscha left 19:31 hankache left 19:48 simcop2387 is now known as simcop2387_, simcop2387_ is now known as simcop2388, simcop2388 is now known as simcop2388_, simcop2388_ is now known as simcop2387-web, simcop2387-web is now known as simcop2387 20:08 dolmen joined 20:15 hankache joined
lizmat logs.liz.nl down for a few minutes to update MacOS 20:15
20:16 ecocode_ joined 20:46 rbt left 20:56 Maylay left 20:57 Maylay joined 20:58 hankache left 21:06 Maylay left 21:08 dolmen left, Maylay joined 21:14 stoned75 left 21:15 ggoebel left 21:21 rheum101 joined 21:23 rheum101 left 21:27 Guest4331 joined 21:31 Guest4331 left, p6steve joined
p6steve made it 21:32
tellable6 2020-08-07T08:37:49Z #raku-dev <JJMerelo> p6steve you ready to upload your article, or you want me to upload it for you?
2020-08-08T07:22:42Z #raku <JJMerelo> p6steve you ready to post that in the blog or are you OK if I do it for you?
hey p6steve, you have a message: gist.github.com/6999c600fb5deda581...4c10e0b6e6
2020-08-09T08:14:27Z #raku <JJMerelo> p6steve I've made some small changes and scheduled your post for tomorrow AM. I would need you to send me your email so that I can invite you to the site and assign authorship of the article to you
[Coke] wow.
21:32 lichtkind joined 21:34 Guest44 joined
p6steve im beginning to think that test is a sweet spot for raku/Cro - any thoughts? 21:35
since there is a http client built in, maybe can build a fleet of Crobots to do perf testing 21:36
21:38 Guest44 left
tonyo on cro itself? 21:39
siege works well
[Coke] (test) wonder if it would also be a good use for the jvm server process. 21:41
21:42 morayj left
p6steve is github.com/JoeDog/siege distributed ... if not then even with lightweight client there will come a point where one server does not stress a server (eg. netflix) 21:44
21:50 linkable6 left 21:53 linkable6 joined, p6steve left 22:02 stigo left 22:03 stigo joined 22:08 p6steve joined 22:12 rbt joined, p6steve left 22:20 Maylay left 22:21 Maylay joined 22:24 p6steve joined 22:25 ecocode_ left 22:28 p6steve left
tyil the Matrix bridge on Libera is in testing now, but still no definite ETA on when it'll become available to the general public 22:29
22:39 p6steve joined 23:39 benchable6 left, releasable6 left, bisectable6 left, shareable6 left, statisfiable6 left, committable6 left, unicodable6 left, greppable6 left, reportable6 left, evalable6 left, linkable6 left, notable6 left, coverable6 left, nativecallable6 left, bloatable6 left, squashable6 left, sourceable6 left, quotable6 left, tellable6 left, unicodable6 joined, statisfiable6 joined, greppable6 joined, bloatable6 joined 23:40 releasable6 joined, benchable6 joined, notable6 joined, nativecallable6 joined, squashable6 joined, evalable6 joined 23:41 committable6 joined, sourceable6 joined, bisectable6 joined, shareable6 joined, linkable6 joined 23:42 quotable6 joined, tellable6 joined, www joined, www left