Welcome to the main channel on the development of MoarVM, a virtual machine for NQP and Rakudo (moarvm.org). This channel is being logged for historical purposes.
Set by lizmat on 24 May 2021.
00:06 reportable6 left 00:07 reportable6 joined 00:18 discord-raku-bot left 00:19 discord-raku-bot joined 00:41 Kaipei left 01:10 rba left, harrow left, rba joined 01:15 harrow joined 01:20 [Coke]__ joined, [Coke] left 02:03 frost75 joined 02:38 frost75 left 04:16 reportable6 left, committable6 left, notable6 left, benchable6 left, bloatable6 left, tellable6 left, nativecallable6 left, sourceable6 left, linkable6 left, shareable6 left, greppable6 left, coverable6 left, quotable6 left, releasable6 left, evalable6 left, bisectable6 left, squashable6 left, statisfiable6 left, unicodable6 left 04:17 shareable6 joined, nativecallable6 joined, reportable6 joined, statisfiable6 joined, notable6 joined, quotable6 joined 04:18 sourceable6 joined, coverable6 joined, greppable6 joined, benchable6 joined, tellable6 joined, bisectable6 joined, bloatable6 joined, committable6 joined 04:19 evalable6 joined, releasable6 joined, squashable6 joined, linkable6 joined, unicodable6 joined 04:31 discord-raku-bot left 05:11 discord-raku-bot joined 05:15 discord-raku-bot left 05:34 discord-raku-bot joined 05:37 discord-raku-bot left 05:40 discord-raku-bot joined 06:06 reportable6 left 06:07 reportable6 joined 07:14 squashable6 left 07:16 squashable6 joined 07:45 sena_kun joined 07:48 Kaipei joined 09:46 evalable6 left, linkable6 left 09:47 linkable6 joined 09:48 evalable6 joined 10:34 Kaipei left 10:56 Kaipei joined
nine jnthn: you ok with taking an updated rakuast branch, renaming it to "main" and using this as the new - well - main branch? I figure it should be safe, as the new compiler frontend is strictly opt-in. I don't see anyone cleaning up the branch's history before a merge and developing on main would lower the entry barrier and help prevent the branch from bitrotting. 11:26
11:29 sena_kun left 12:07 reportable6 left 12:08 reportable6 joined 12:32 Kaipei left 12:41 Kaiepi joined 13:59 MasterDuke joined
MasterDuke i just realized the downside to github.com/MoarVM/MoarVM/pull/1723 is that the libuv functions are not implemented on windows 14:01
tellable6 2022-10-24T00:39:46Z #moarvm <japhb> MasterDuke: Yeah, sorry, thumbs-up from me.
MasterDuke but i feel we must have some other subs/methods in raku that are OS-specific? 14:02
jnthn nine: What if people then depend on RakuAST stuff when there's no doubt things that will have to be changed? 14:05
Geth MoarVM: c69534c6d6 | (Daniel Green)++ | 8 files
Add chown op

Just a thin wrapper around `uv_fs_chown()`, inspired by
MoarVM: d222233818 | MasterDuke17++ (committed using GitHub Web editor) | 8 files
Merge pull request #1723 from MasterDuke17/add_chown_op
nine jnthn: Well, truth is, I just don't know what else to do. In the 3 months I was stuck on that stupid problem, there was 0 progress on RakuAST and even worse: it actually fell further behind, as there were changes to the old frontend. I wonder if that isn't a greater danger than early adopters having to...well adopt some more. 14:13
MasterDuke OT, but would this (docs.python.org/3.11/whatsnew/3.11...e-objects) be something we could steal? 14:39
or would that require coupling moarvm and rakudo too closely? 14:42
japhb jnthn: Since the new compiler frontend would still be strictly opt-in, I don't think people could *accidentally* rely on RakuAST ... but I do understand the concern about people who might develop very large amounts of RakuAST code, hoping to push it to zef as soon as RakuAST becomes default, and forcing them to rework that boulder a few times. 15:35
16:03 Kaiepi left 16:08 Kaiepi joined 16:36 squashable6 left 16:38 squashable6 joined 16:40 jjatria left, Geth left, JRaspass left 16:41 ilogger2 left, Techcable left, epony left 16:42 epony joined 16:43 Techcable joined 16:53 jjatria joined, JRaspass joined, ilogger2 joined 18:07 reportable6 left 18:10 reportable6 joined 18:20 MasterDuke left 19:58 Geth joined
japhb Forgot to write this in channel -- spoke to jnthn today about RakuAST as main: he's fine with it as long as 1) the new compiler frontend remains opt-in-only, 2) access to RakuAST classes requires a 'use experimental', 3) people who are chomping at the bit to get started converting stuff to RakuAST are warned explicitly, again, that there *will* be API changes before it is "done", and early adopters will be 20:49
left holding the pieces if their forward-looking code breaks.
20:50 epony left 20:51 epony joined 21:18 squashable6 left 21:19 squashable6 joined 21:24 [Coke]__ left 22:54 epony left 23:54 committable6 left, bloatable6 left, nativecallable6 left, notable6 left, quotable6 left, shareable6 left, evalable6 left, bisectable6 left, benchable6 left, statisfiable6 left, greppable6 left, unicodable6 left, squashable6 left, reportable6 left, tellable6 left, sourceable6 left, coverable6 left, linkable6 left, releasable6 left, notable6 joined 23:55 committable6 joined, sourceable6 joined, shareable6 joined, squashable6 joined 23:56 greppable6 joined, evalable6 joined, linkable6 joined, releasable6 joined, quotable6 joined, bloatable6 joined, benchable6 joined, reportable6 joined 23:57 bisectable6 joined, coverable6 joined, tellable6 joined, nativecallable6 joined, statisfiable6 joined, unicodable6 joined