| 13 Apr 2026 | |||
| apogee_ntv | tbh I thought notcurses did this automatically. | 11:39 | |
| librasteve_ | all good with Ctrl-Q -tx! | 12:25 | |
| apogee_ntv | Sweet, let me know if you hit anything else. BTW there are full API docs at github.com/m-doughty/Selkie/blob/m...i/index.md -- will get a site up at some point to make this stuff easier to navigate. | 12:32 | |
| disbot2 | <librasteve> is there a way to check whether a zef package is a new module release? I am thinking of diff ing 360.zef.pm/ from week to week, but that seems like quite a lot of effort and there may well be a better way?? | 14:49 | |
| [Coke] | raku.land/zef:coke/App::Cal, for example, shows "7 Feb 2024" as the release date for the current version. | 15:32 | |
| but that info doesn't seem to be in 360.zef.pm/ | 15:33 | ||
| wondering if raku.land is pulling that from the git repo or its logs. | |||
| a hygenic git repo has, e.g.: github.com/coke/raku-cal/releases/tag/0.9.1 | 15:34 | ||
| (but you can't rely on authors doing that even if they do use github) | 15:35 | ||
| disbot2 | <antononcube> @librasteve The most topical new package release is this one: raku.land/zef:antononcube/WWW::Hor...erisSystem | ||
| <librasteve> just in time ;-) | 15:40 | ||
| <antononcube> Didn't have time to implement the 3D trajectory plotting. (In Raku.) | 15:41 | ||
| <antononcube> I plan to do it this week. | |||
| <librasteve> [Coke] thanks ... yeah I already automated grabbing the "most recent" from that page, but I am trying to avoid screen scraping the actual module page release date history drop down | 15:42 | ||
| <librasteve> I will probably just make a list of all modules manually, store as keys to a .raku hash and then append to it each week ;-) | 15:44 | ||
| librasteve_ | notable6: weekly | 15:45 | |
| notable6 | librasteve_, 6 notes: gist.github.com/e2b318fa9486dc354f...a6efa72cf0 | ||
| librasteve_ | notable6: weekly reset | 15:47 | |
| notable6 | librasteve_, Moved existing notes to “weekly_2026-04-13T15:47:15Z” | ||
| librasteve_ | bot test raku.org/tools | 15:49 | |
| MOAR#768 | |||
| linkable6 | MOAR#768 [closed]: github.com/MoarVM/MoarVM/issues/768 Buncha warnings when compiling on Win10 using Strawberry Perl suite's compiler | ||
| librasteve_ | rtfm | ||
| buildable6: status | 15:50 | ||
| disbot2 | <librasteve> .hug | 15:51 | |
| huggable6 hugs librasteve | |||
| librasteve_ | rakudoweekly.blog/2026/04/13/2026-...gs-busses/ | 18:00 | |
| ugexe | m: my $x = <1>; sub foo(Int() $y) { say $y.WHAT; $y; }; say foo($x) | 18:50 | |
| evalable6 | (IntStr) 1 |
||
| ugexe | m: my $x = <1>; sub foo(Int() $y) { say $y.WHAT; $y; }; say foo($x).WHAT | 18:51 | |
| evalable6 | (IntStr) (IntStr) |
||
| lucs | irclogs.raku.About a week ago, instead of using --force-fetch to grab a module with zef, I obtained and installed the raw.githubusercontent.com ca certificate, which permitted the fetch. | 19:31 | |
| (Oops, spurious URL at the beginning there.) | |||
| Now today, I'm getting the same problem. | |||
| Obtained the certificate, and it appears to have changed. | |||
| Does it keep doing that? | 19:32 | ||
| avuserow | raw.githubusercontent.com is signed by Let's Encrypt so it will rotate quickly | 19:33 | |
| lucs | Ah, hmm... | 19:34 | |
| avuserow | the CA cert shouldn't change that often though | ||
| lucs | I'm not sure I'm doing this correctly, but I obtain the certificate with `openssl s_client -connect raw.githubusercontent.com:443 -showcerts` | 19:36 | |
| avuserow | Let's Encrypt should be trusted by basically all OSes trust stores, for what it's worth. but I am probably missing context on why you need to verify it directly | ||
| lucs | My (limited) understanding is that once obtained, something like this is necessary (Slackware Linux): `cp the-certif.crt /usr/local/share/ca-certificates; update-ca-certificates` | 19:38 | |
| Worked last time, will try with today's certificate to see... | 19:39 | ||
| avuserow | you want to put a CA cert into your store (like from letsencrypt.org/certificates/ or equivalent), not the leaf one that's served up. then the CA cert can be used to validate any new leaf cert. (leaf cert is probably not quite the right term but the idea holds) | 19:41 | |
| lucs | I think I see what you mean. I'll aim for that. | 19:44 | |
| avuserow | I'm looking for some NativeCall advice. I'm trying to send a CArray of structs to a function that's like `void doSomething(MyType *stuff)`. If I define it as `sub doSomething(CArray[MyType]) is native(...)` then it gets sent as a MyType** rather than MyType*. I'd appreciate some pointers (heh) if anyone has done this | 20:16 | |
| stackoverflow.com/questions/646842...-raku-to-c has a workaround for this situation but I was hoping there was a core-provided way since then | |||
| (otherwise I'd probably prefer to write a small C wrapper function myself since that seems safer/cleaner, at the cost of introducing a compiler step) | 20:17 | ||
| apogee_ntv | avuserow: Wrapping is the least painful option. | 23:32 | |
| Saying this as someone who writes a lot of nativecall, unless you want to abuse Buf and manually align struct fields... wrap it :D | 23:33 | ||
| 14 Apr 2026 | |||
| avuserow | Technically there's another option for this struct in particular. It's only four `num32` fields so I can make it a `CArray[num32]` (for now) | 00:07 | |
| apogee_ntv | www.reddit.com/r/rakulang/comments..._for_raku/ Posted some example video. | 03:29 | |
| x-posted to some terminal subs too, try to drive some traffic to Raku | 03:30 | ||