🦋 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.
04:11 MasterDuke left 07:52 sena_kun joined 09:11 finanalyst joined
Geth rakudo/rakuast-phase-cleanup: 34 commits pushed by (Jonathan Worthington)++, (Stefan Seifert)++
review: github.com/rakudo/rakudo/compare/6...3dec282a74
11:52
ab5tract nine++ 12:11
What’s the test count up to in that branch?
nine 1058 12:25
-7+2 compared to main
ab5tract so close! 12:40
congratulations on making such swift work on that
Geth rakudo/main: 5748ac2022 | (Elizabeth Mattijsen)++ | 3 files
RakuAST: =place needs a URI, not a URL
12:52
14:04 Xliff joined
Geth rakudo/main: 774cc86410 | ab5tract++ | src/core.c/IO/Handle.rakumod
Improve .IO.open.lock failure messages

The previous behavior:
   > raku -e '"foo".IO.open(:w).lock(:shared)'
   Could not obtain blocking, shared lock: Failed to lock filehandle: 9
... (11 more lines)
14:10
ab5tract going to migrate $!mode to the NQPFileHandle 14:26
lizmat nine: re 2cba37f5c4101d39f2fd , don't we have a similar issue in NQP ? 14:52
linkable6 (2024-05-12) github.com/rakudo/rakudo/commit/2cba37f5c4 Fix mysterious failures when class construction process order changes
nine lizmat: I guess we'd have noticed by now 14:56
lizmat yeah.. well hidden bugs... could be too well hidden
I guess the answer is really: possibly, but unlikely ? 14:57
nine yep 15:03
lizmat ok, will investigate later this week 15:10
ab5tract came across this and couldn't help wonder if it could be related as well: R#1419 15:14
linkable6 R#1419 [open]: github.com/rakudo/rakudo/issues/1419 A simple change of `use` ordering causes a surprising breakage
nine Sounds more like global merging insanity 15:16
ab5tract figured it was a long shot, but thought I'd mention it 15:46
lizmat notable6: weekly 15:59
notable6 lizmat, No notes for “weekly”
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2024/05/13/2024-...nnouncing/ 17:23
17:54 finanalyst left 18:12 hankache joined 18:29 finanalyst joined 18:33 finanalyst left
Geth nqp-configure: AntonOks++ created pull request #28:
Config.pm: Windows: Ensure x64 architecture
19:12
¦ rakudo: lizmat self-assigned Error in LibCurl with v2024.04-82-gecd2dd469. github.com/rakudo/rakudo/issues/5567 19:13
¦ rakudo: lizmat self-assigned New type Block for List is not a mixin type github.com/rakudo/rakudo/issues/5563 19:15
rakudo/main: 46a8f32472 | (Elizabeth Mattijsen)++ | 2 files
Make sure all expected identifiers are available

In the streamlining of NativeCall, quite a few identifiers were not exported and/or not available in places where some modules
  (such as NativeLibs) expect them to be. This did not lead to
any (spec)test failures, but it did lead to some breakage in the ecosystem, as reported in: ... (7 more lines)
19:51
20:55 hankache left 23:40 sena_kun left