|
00:42
eseyman left
00:44
eseyman joined
01:47
hulk joined
01:48
kylese left
02:15
hulk left,
kylese joined
03:30
dicit joined
05:50
dicit left
05:56
Sgeo left
06:06
abraxxa joined
06:08
abraxxa left
08:02
vrurg_ joined
08:04
vrurg left
08:19
grondilu left
08:36
grondilu joined
|
|||
| disbot | <demanddystopia> Is there a reason that is/can't? be a thing openly documented) | 09:26 | |
|
09:28
DemandDystopia joined
|
|||
| lizmat | if it's about the release process, it *is* documented afaik ? | 09:29 | |
| DemandDystopia | Though the way it's chained rakudo ← nqp ← moarvm got obvious when I once wanted to see how exactly `.is-prime` was implemented which seems to go through the entire chain & ends in a c file | 09:32 | |
| lizmat | yeah, but that's pretty rare | 09:33 | |
| nqp::time is another one like that | |||
| Voldenet | heh, I remember needing process id before it was returned from Proc::Async, so I made an op for extracting that info from libuv, which made me cut across all the layers too | 09:35 | |
| lizmat | ah, yes, nqp::getpid | ||
|
09:36
DemandDystopia13 joined,
DemandDystopia left
|
|||
| Voldenet | implementing a new op is unique experience, that's for sure | 09:36 | |
|
09:37
DemandDystopia13 left
|
|||
| Voldenet | but also makes one grasp how compilation is done and also all the layers | 09:37 | |
|
09:38
DemandDystopia joined
|
|||
| Voldenet | (though if I implemented this today, I'd probably use nativecall and quick and dirty lib linked to libuv from moar…, definitely less work) | 09:38 | |
| DemandDystopia | Definitely wanna get some understanding of how the entire conpiler clicks today one day. Picked up Raku like 2–3 months ago and became really enamored with the introspection & "I can't believe this works" type stuff, which leads to eventually the best documentation being the actual source or grammar | 09:47 | |
|
09:59
DemandDystopia left
|
|||