🦋 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: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
01:11 coleman left 01:12 coleman joined 01:13 coleman left 01:14 coleman joined 01:19 notable6 left, notable6 joined
[Coke] coleman: you have insight into the whateverable bots 03:27
coleman I do not, unfortunately 03:41
I could try to deploy but it would be a new deployment 03:42
I'll look tomorrow
off to bed now
05:11 notable6 left, notable6 joined 05:13 nativecallable6 left 05:15 greppable6 left 05:24 kjp left 05:25 committable6 left 05:26 kjp joined 05:28 kjp left 05:29 kjp joined 08:29 finanalyst joined 08:38 finanalyst left 09:19 notable6 left, notable6 joined 10:34 finanalyst joined 11:12 bisectable6 left, coverable6 left, notable6 left, benchable6 left 11:13 quotable6 left, sourceable6 left 11:15 bloatable6 left 11:27 nativecallable6 joined 11:28 quotable6 joined, greppable6 joined, benchable6 joined, evalable6 joined 11:29 sourceable6 joined, releasable6 joined, linkable6 joined, coverable6 joined, committable6 joined, bloatable6 joined 11:30 shareable6 joined 11:31 unicodable6 joined, notable6 joined, tellable6 joined 11:35 bisectable6 joined 12:14 finanalyst left 13:15 finanalyst joined
timo hmm. i feel like the docs should really point out that ARGFILES / CatHandle will close each handle in turn when you iterate over its .handles 14:42
ugexe it has always felt like those were poorly thought out, similar to other apis we have designed to make something already easy even easier for some reason 14:49
reactive programming 14:50
or maybe reactive designing is a better term 14:51
timo argfiles was in order to make something equivalent to `while (<>) {` work, right? 15:03
it does make sense that CatHandles wouldn't be the right thing for zipping all specified files. it's cat after all, not ... uh ... zebra? 15:04
15:09 kjp left 15:10 kjp joined 15:11 finanalyst left
ugexe presumably, but that is sort of what i'm talking about. CatHandles is really more like <<>> in perl, but was seemingly implemented and sold as if it was <> 15:13
timo can you elaborate? i don't perl much at all, you see 15:19
ugexe <> uses two arg open and thus lets you do a lot more things... potentially dangerous things but you can do dangerous things with what it is meant to emulate (awk/sed behavior, pipes). for example in perl could write `while (<*.rakumod>) {` 15:23
jdv tu 15:34
oops
timo i only vaguely recall something about two arg open being problematic. three arg open is where you also put an explicit mode in it, like "<" or ">" for reading or writing respectively?
ugexe yes. but what do you presume <>/<<>> was being used for in perl? my presumption is it is mostly used for one liners and throw away scripts, scenarios where you generally are open to using powerful footguns 15:35
like i don't recall actually seeing anyone use <<>>
it is trivial to iterate over filenames and do precisely whatever you want in raku. yet that is the only part of the <> from perl that was implemented 15:38
timo what use cases besides reading all lines from all files by pattern would there be? you can't safely write to a text handle in the middle of a file, right? unless what you do doesn't have to move parts of files around of course 15:46
you have special variables for stuff like currently opened file name, current line number, stuff like that right? and presumably also the file handle itself is reachable 15:47
does the "in place" flag for perl make it possible to like, stream-transform files line-by-line, i wonder? 15:49
ugexe i don't think there is another good use case, no. in perl it is a powerful footgun, and those things make sense for one liners. in raku we did not get the powerful footgun <>, we got the the neutered/safer version <<>> which is not as useful for one liners. so our api around that ultimately accommodated the wrong use case imo, and it probably came about because someone requested to do the simple 16:02
"process each file" / <<>> behavior
timo OK I think I understand 16:07
17:07 finanalyst joined 18:18 librasteve_ joined 18:58 AlexDaniel joined
AlexDaniel . 18:58
tellable6 2025-05-10T22:21:41Z #raku-dev <jdv> alexdaniel wut? idk.
AlexDaniel c: HEAD say 42
committable6 AlexDaniel, ¦HEAD(1464a0f): «42␤»
AlexDaniel I was outside of town. During that time, the server froze. Eventually, this was automatically detected and it was sent into a hard reboot. I guess that's when the bots went back up 18:59
if anybody is willing, we can deploy them on your infra. Just need to transfer the builds and set up docker. 19:00
Geth rakudo/main: 2ec173ab07 | (Elizabeth Mattijsen)++ | src/Raku/ast/expressions.rakumod
RakuAST: Alternate fix for #5883

A less hacky way, as suggested by nine++		 19:09
rakudo: patrickbkr++ created pull request #5888:
Change Linux pre-built release pipeline, CentOS 7 -> Ubuntu 16.04		 20:33
japhb I think my brain broke a little reading that PR title 20:38
Geth whateverable/main: 751467e3df | (Aleks-Daniel Jakimenko-Aleksejev)++ | lib/Whateverable/Discordable.pm6
Update the discord bot name again

Not sure what the second fallback is, but probably one of those.
Context: irclogs.raku.org/raku/2025-05-25.h...20:47-0001		 20:50
rakudo/main: 72bf08fc73 | (Patrick Böker)++ | 3 files
Change Linux pre-built release pipeline, CentOS 7 -> Ubuntu 16.04

Azure removed support for the Ubuntu 20.04 agent OS. We need to mount the docker binary into the container to work around missing root permissions in the container. That only works when the host's docker binary is glibc compatible with the container glibc. Upgrading Ubuntu from 20.04 to 22.04 made the host's docker binary incompatible with CentOS' 7 glibc. ... (10 more lines)		 20:52
rakudo/main: 7783e28b82 | (Patrick Böker)++ (committed using GitHub Web editor) | 3 files
Merge pull request #5888 from patrickbkr/azure-linux-fix

Change Linux pre-built release pipeline, CentOS 7 -> Ubuntu 16.04
20:54 shareable6 left, linkable6 left, releasable6 left, committable6 left, nativecallable6 left, bloatable6 left, greppable6 left, bisectable6 left, benchable6 left, notable6 left, tellable6 left, sourceable6 left, unicodable6 left, quotable6 left, coverable6 left, evalable6 left 20:57 linkable6 joined, nativecallable6 joined, quotable6 joined, bloatable6 joined, greppable6 joined 20:58 coverable6 joined, notable6 joined, committable6 joined, tellable6 joined, unicodable6 joined, evalable6 joined, shareable6 joined 20:59 bisectable6 joined, benchable6 joined, releasable6 joined 21:00 sourceable6 joined 21:23 AlexDaniel48 joined 21:24 AlexDaniel left 21:57 AlexDaniel48 left
patrickb and finally the pre-built release pipeline is working again and the Linux binaries for 2025.05 are released. 22:02
lizmat patrickb++ 22:04
tellable6 hey lizmat, you have a message: gist.github.com/8e44117b654ad07f05...ff6c9de9c0
lizmat thanks tellable6 22:05
tellable6 lizmat, Thank you! You love me, you really love me!
22:07 librasteve_ left

Powered by Cro and the Raku® Programming Language.

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

Thank you!