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.
lizmat ugexe: how can that be thread safe ? 07:57
or does libuv guarantee that ? 07:58
ugexe Stating a file twice isn’t any more thread safe 11:11
nine I think the best way to do this would be to add a REPR for wrapping uv_stat_t and one or more syscalls to access the information contained in it. 12:28
A working, but worse in every regard solution would be to create a BOOTHash containing the stat buffer's information and pass that to user space.
[Coke] I love that description. 12:39
ugexe nodejs does the later 13:40
leont Is anything needed to get github.com/MoarVM/MoarVM/pull/1756 merged? 18:14
And yes, exposing some sort of stat_t would be most welcome 18:15
I've been wanting that for years
lizmat leont: lemme merge it
anything needed as a followup?
leont There's an accompanying branch on rakudo that actually uses it 18:16
lizmat is that in a PR also ?
Geth MoarVM/main: 3df20182bb | (Leon Timmermans)++ (committed using GitHub Web editor) | 3 files
Add ops for unix domain sockets

Add async unx domain socket connect/listen and syscalls for async unix domain sockets
leont That's github.com/rakudo/rakudo/pull/5269 18:17
lizmat oki
rakudo PR also merged, leont 18:34
leont \o/
lizmat anything in roast that needs merging ?
hmmm... looking at the code: this will only work on the MoarVM backend, right? 18:35
MasterDuke i thought timo1 had some stat PR, but i guess i was thinking of github.com/MoarVM/MoarVM/pull/536 21:03
nine: why would the BOOTHash be worse in every regard? 21:04
also, the stat constants are small and pretty contiguous, it could be an array instead of a hash 21:05