00:05 arkiuat joined 00:13 arkiuat left
Voldenet it's not actually impossible to compile raku into binaries - in fact given some specific AST it's possible to write C directly from it 00:16
generating C from tiny subset of the language should be trivial due to having built-in parser for it 00:19
for example "all types must be defined, only Str and Int are supported, only simple subs" should be relatively easy, types for scopes, signatures would need to be practically implemented in C 00:24
otoh, scopes, dynamic variables, await can't be written in trivial C, so that'd require bundling the whole raku runtime - it's not impossible to generate bytecode and use this path 00:27
00:27 arkiuat joined
Voldenet at some point I was planning to build some poc of embeddable raku (something like PerlInterpreter), it would definitely make this more feasible 00:30
arkiuat some Str somewhere isn't getting initialized. I think this is the kind of thing that made me flee *brew and scurry back into MacPorts (which hasn't updated rakudo since v2025.05) 00:33
Voldenet hm, is there any stack trace? 00:34
01:03 notable6__ joined, quotable6 left, notable6 left, bisectable6 left, linkable6 left, Ekho left, cryosis left, unicodable6 left, sourceable6__ left, coverable6 left, benchable6 left, releasable6 left, quotable6 joined, bisectable6 joined, linkable6 joined 01:04 nativecallable6_ left 01:05 nativecallable6 joined, zetaaaa_ left, Sgeo__ joined 01:06 cryosis joined, Ekho joined 01:07 benchable6 joined 01:08 Sgeo_ left
arkiuat Nope, it's a compilation error 01:08
pointing to /private/var/folders/p2/ with what look like hashes in the rest of the path 01:09
It happened most recently when I was installing ValueType and then later with App::Ecosystems 01:11
just now I tried "zef install rakudoc" -- same compilation error 01:12
perhaps when I decided to try *brew again, I needed to thoroughly eradicate MacPorts from my system first. Not sure that I've done that correctly 01:14
okay, this is fun. I just used rakubrew to switch from v2025.08 back to v2025.05, and now ValueType just installed with no problem, and rakudoc is installing 01:18
installed successfully, and now installing App::Ecosystems. So this seems to be a bug introduced in v2025.08 maybe? 01:19
01:21 hulk joined, kylese left 01:22 zetaaaa_ joined
arkiuat that failed, but for a much more graspable reason: expected module eigenstates v0.0.11 but got eigenstates v0.0.12 01:22
01:29 nine left 01:30 nine joined
Voldenet hmm, ValueType doesn't have very large test, maybe it could be further reduced to one line 01:32
arkiuat yes, that's a good tip 01:59
the compilation error singled out line 2 of the single test file, which is "use Test" which would certainly explain why this is happening across all modules! 02:04
however, "raku -MTest" under v2025.08 starts up with no problem 02:06
02:15 hulk left, kylese joined 02:49 zetaaaa_ left 03:08 arkiuat left 03:20 arkiuat joined 03:24 arkiuat left 03:25 dg left 03:26 dg joined 03:44 arkiuat joined 03:54 arkiuat left 04:36 Aedil joined 05:22 phogg left 05:27 phogg joined 06:26 Geth left 06:27 Sgeo__ left 06:28 kylese left 06:29 kylese joined 06:45 quotable6 left, cryosis left, quotable6 joined, bisectable6 left 06:57 dg left, timo2 left, timo2 joined
disbot9 <simon_sibl> I am not sure to understand the do whenever at docs.raku.org/type/IO/Socket/Async/ListenSocket why is the do required, why is the return value handled that way ? 06:58
07:00 dg joined 07:10 tadzik joined 07:13 merpp left, merp joined
disbot9 <simon_sibl> also, will Raku recognize such instruction and use sendfile or similar trick: $socket.write($path.IO.slurp(:bin)) ? or it will slurp the whole file in memory and only then send it through the socket ? 07:48
<simon_sibl> or linked to that question, would it be possible to lazily read a file, pipe it through a base64 generator and lazily send that output through a socket ? 07:50
08:09 dakkar joined 08:44 Maylay left 08:46 lichtkind_ joined 08:47 Maylay joined