🦋 Welcome to the MAIN() IRC channel of the Raku Programming Language (raku.org). Log available at irclogs.raku.org/raku/live.html . If you're a beginner, you can also check out the #raku-beginner channel!
Set by lizmat on 6 September 2022.
01:53 jgaz left 01:58 _________ left 02:07 hulk joined, kylese left 02:09 wbooze left 02:15 _________ joined 02:33 Aedil joined 02:57 swaggboi left 03:00 swaggboi joined 03:15 hulk left, kylese joined 03:30 Aedil left 03:38 Aedil joined 03:56 maylay left 03:58 maylay joined 04:30 kylese left 04:32 kylese joined 04:33 jpn joined 04:37 jpn left 05:30 kylese left, kylese joined
melezhik. [Coke]: it’s fresh install indeed. ugexe: I am still not sure what you are trying to say, there is certainly delay here , we just don’t know why whst cause it, to eliminate any side effects of CI I will probably run zef install Air on docker container manually and see what it does . With regard to buffering - if this is the case why then we don’t see buffering/delays on other lines ? Also I am 99% I disable 05:33
buffering in my code … by anyways we will see what it does when gets run without any ci layer Also I have noticed such a behavior of zef ( a significant search stage even for small number of dependencies) many times on all other environments
05:58 yewscion_ left 06:02 jpn joined 06:07 jpn left 07:35 yewscion_ joined 07:45 yewscion_ left
librasteve thanks for trying Air both from a CI and a user point of view … please bear in mind that Air is the glue in the “HARC stack” that’s HTMX, Air, Red & Cro so zen install Air has a lot of heavy lifting to do … that’s why, in the Getting Started I say 07:49
Install Air, Cro & Red - zef install --/test cro - zef install Red --exclude="pq:ver<5>" - zef install Air``` 07:50
this manual instruction is needed on my macOS to force Cro and Red to install in a reasonable time … I don’t know what the exclude on Red is doing. right now this works on my machine on 2024.10 but I cannot get Red to install in 2025.02 07:52
the point of saying this in the getting started is to lift installing Cro and Red to the fore and for users to hit any errors on these directly and can seek help on their respective authors due to their size and complexity (and that I do not know much about eg Red install deps) 07:55
it is not surprising that these modules struggle on CI since afaik we cannot adverb in META6.json like —\test … I would happily add these if we had them … another option I guess is to go `zen Air —\test’ but that seems to defeat the whole idea 07:58
08:02 jpn joined 08:07 maylay left 08:08 maylay joined 08:12 yewscion_ joined, jpn left 08:16 yewscion_ left 08:38 jpn joined 08:46 Geth left, lizmat left, Geth joined 08:47 lizmat joined 08:58 melezhik joined
melezhik librasteve: thanks, but I use Air as an example of slow zef ( Raku ? ) performance during installation , but like I said it happened to me with many other modules 09:01
09:01 melezhik left 09:03 Sgeo left 09:08 jpn joined 09:13 jpn left 09:17 yewscion_ joined 09:22 yewscion_ left 09:27 sena_kun joined 10:31 jpn joined 10:36 jpn left 10:57 yewscion_ joined 11:02 yewscion_ left 11:11 abraxxa-home joined 11:22 Aedil left
wayland76 Just wanted to say I'm joining up to Discord, and in the "Info and Rules" channel, there's a bunch of messages that refer to other channels. All those channel names are currently invisible (ie. they just say "No Access") because I don't belong to them. I don't know if this is something that needs fixing, but thought I'd mention it. 11:40
11:40 abraxxa-home left 11:41 abraxxa-home joined 11:46 wayland76 left 11:49 wayland76 joined 11:50 wayland-mobile joined 11:54 jpn joined 11:59 jpn left 12:18 jpn joined 12:23 jpn left
librasteve wayland76: I have checked and the info and rules references should be visible (ie they refer to channels that still exist and that I can see) you are not missing much the occasional post on showcase and raku-beginner are busiest 12:26
maybe there is a way to search for / join channels on the discord server in the app, i don’t remember what i did back in the day 12:27
there’s a chance you didn’t notice the drop down arrows 12:31
otherwise, whoever is admin may need to check permissions…
wayland-mobile Also, before I joined, I used the discord search to search for Raku, and it didn't show up. 12:37
I think the only way you could fix it would be to make the channel names not actually be linked to the channels (could they be included in code blocks?) 12:39
(that second message referred to the first problem, not the second) 12:40
12:42 bazzrrr0 joined
bazzrrr0 m: my @a = (1, 2, 3); say @a; my %h = %('a',@a); say %h{'a'}; 12:49
camelia [1 2 3]
[1 2 3]
12:49 wayland joined 12:50 wayland76 left 12:53 habere-et-disper joined
bazzrrr0 m: my @a = (1, 2, 3); say join(',', @a); my %h = %('a',@a); say join(',', %h{'a'}); 12:53
camelia 1,2,3
1 2 3
12:55 apac left
bazzrrr0 if I have a tin of beans, and inspect it, then stash the tin as a keyed value in a hash, and inspect again, should it not be the same tin of beans? 13:01
lizmat thing is: when you store it in an array like that, it gets another tin around it 13:02
m: my @a = (1, 2, 3); say join(',', @a); my %h = %('a',@a); say join(',', %h{'a'}<>);
camelia 1,2,3
1,2,3
lizmat the <> removes the outer tin
normally you don't notice the outer tin (aka container) 13:03
but for iterable values, it does matter: it they're in a container, they're considered a *single* value
m: my @a = (1, 2, 3); say join(',', @a); my %h = %('a',@a); say %h{'a'}; # the join didn't join anything 13:04
camelia 1,2,3
[1 2 3]
lizmat m: my @a = (1, 2, 3); say join(',', @a); my %h = %('a',@a); say %h{'a'}.Str; # but just stringified
camelia 1,2,3
1 2 3		 13:05
13:06 jpn joined
bazzrrr0 I see, thanks lizmat for explaining why the behaviour is so, and for showing the <> operator usage :-> 13:08
13:08 lizmat_ joined 13:10 lizmat left 13:11 jpn left 13:15 lizmat_ left, lizmat joined
bazzrrr0 I guess I'm wondering if the extra container should be automatically removed if the value is extracted from the hash, but I'm sure it's been discussed previously. 13:16
lizmat you don't want that
m: my %h = a => 42; say %h<a>; %h<a> = 666; say %h<a> 13:17
camelia 42
666
lizmat otherwise ^^ wouldn't work
13:47 bazzrrr0 left 14:07 jpn joined, Aedil joined 14:12 jpn left 14:26 maylay left 14:27 abraxxa-home left 14:28 maylay joined 14:47 melezhik joined
melezhik o/ 14:48
14:48 melezhik left 14:54 habere-et-disper left 15:08 jpn joined 15:13 jpn left 16:03 maylay left 16:05 maylay joined 16:09 jpn joined 16:14 jpn left 16:33 bazzrrr0 joined 17:07 yewscion_ joined
bazzrrr0 Just wanna say, from my hobbyist standpoint, Raku totally rocks! wrote myself a script that tackles a [PDF::Extract] html extract of a specific PDF document, and fixes the inconsistencies in the document, so ending up with a usable dataset. I couldn't imagine how I could do the same in another language, say Python, as the ease of use of Raku makes 17:09
the "debugging and trial and error, and where next" aspect of programming all just part of the application thought process.
17:10 jpn joined
bazzrrr0 tried to post ^^ earlier but it seems like the client was disconnected at the time, as the comment didn't appear in the chat log. 17:11
17:12 yewscion_ left
antononcube @bazzrrr0 Most likely the procedure you outline can be done as easily with Wolfram Language (WL). But WL's code would be longer than Raku's. 17:14
17:15 jpn left 17:16 bazzrrr0 left
Raku is terser when it comes to string manipulation. 17:17
17:20 LainExperiments joined, LainExperiments9 joined 17:24 coleman left, LainExperiments left 17:27 LainExperiments9 left 17:47 habere-et-disper joined 17:52 yewscion_ joined 17:57 yewscion_ left 18:05 lichtkind joined 18:11 jpn joined 18:13 Sgeo joined 18:16 jpn left 18:18 LainExperiments joined 18:20 stanrifkin joined 18:26 LainExperiments7 joined 18:28 LainExperiments left 18:30 jpn joined 18:32 LainExperiments7 left 18:35 LainExperiments joined 18:41 Altai-man joined, sena_kun left 18:44 wbooze joined 18:45 habere-et-disper left 18:54 coleman joined 19:19 Altai-man left, sena_kun joined 19:23 sena_kun left 19:25 sena_kun joined 19:26 bazzrrr0 joined
bazzrrr0 antononcube thanks for the comment re. Wolfram language and string manipulation, I will try to check it out, maybe even install it too :-) 19:35
19:45 sena_kun left 19:46 sena_kun joined 19:48 sena_kun left 19:49 sena_kun joined 19:54 jpn left 20:00 bazzrrr0 left 20:07 wbooze left 20:19 Aedil left
SmokeMachine Would someone like to proofread a new blog post? dev.to/fco/the-future-of-red-orm-f...ug-8151519 20:32
it's heavily edited by chatgpt... 20:33
[Coke] SmokeMachine: 404
SmokeMachine what about now? dev.to/fco/the-future-of-red-orm-for-raku-44gf 20:34
[Coke] :ok: 20:37
20:37 maylay left
SmokeMachine weekly: dev.to/fco/the-future-of-red-orm-for-raku-44gf 20:38
notable6 SmokeMachine, Noted! (weekly)
20:39 Guest69 joined, maylay joined
[Coke] benefits for developer bullet points have a lot of capitalization that seems unnecessary. 20:39
Only style note is that I personally would prefer more monospace stuff when referring to code/specific attributes outside of a full code block, but that's not a hard rule. Otherwise seems fine. 20:40
e.g. I'd monospace the WHERE in WHERE clause. 20:41
but again, personal pref.
coleman SmokeMachine++ that is a great explanation of the power of RakuAST 20:54
[Coke] Sorry, should have led with that. :)
was more "did you spell things right, use apostrophes..." :) 20:55
SmokeMachine About the styling, I’m not really sure about how to change it… :( 20:58
[Coke] eh, no worries 20:59
SmokeMachine [Coke]: I did change the capitalisation, is it looking better now? 21:07
[Coke] Yes, thanks
SmokeMachine Thank you! :) 21:08
21:17 LainExperiments left
librasteve SmokeMachine: proof reads good to me 21:33
SmokeMachine Thanks 21:35
22:05 lizmat_ joined, lizmat left 22:10 sena_kun left 22:11 wayland left 22:16 yewscion_ joined 22:22 yewscion_ left 22:29 apac joined 22:37 stanrifkin left 22:52 lichtkind left 23:10 maylay left 23:14 sena_kun joined, maylay joined, sena_kun left
[Coke] El_Che, patrickb: 2025.03 release is available on github 23:33
23:33 jpn joined
[Coke] Hopefully a little smoother to digest than the 2025.01 was. 23:33
23:37 jpn left
jdv woohoo 23:37

Powered by Cro and the Raku® Programming Language.

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

Thank you!