IRC channel logs

<jfred>msavoritias: It's been a couple days but isolating IO to its own vat is an approach I've taken before and feels like a pretty clean way to go. Goblins also now has this though, which I haven't played around with yet but looks nice: https://spritely.institute/files/docs/guile-goblins/0.14.0/IO.html

<dthompson>oh msavoritias is back! I was going to reply yesterday but they weren't online

<dthompson>thanks jfred that is exactly the link I wanted to send

<msavoritias>o/

<jfred>ACTION should probably read through the Dissecting Guix posts and try to grok them too though

<jfred>I can't say I really understand monads yet :)

<dthompson>the ^io actor is the thing to use. it handles all the annoying stuff.

<msavoritias>thanks jfred :D i didnt know there was IO! yeah definetily im going with that then

<dthompson>it's relatively new but we have used it a bunch

<jfred>no problem :)

<dthompson>if you know how to work with scheme ports, then you're most of the way there to knowing how to work with io actors

<dthompson>the io actor will wrap a port object and you'll do read/write ops by sending messages to it

<jfred>that does sound like exactly what you'd want, haha

<dthompson>the only thing you may have to set up in advance is to make the port nonblocking, in the case of a socket

<dthompson>the io actor will take care of the rest and make sure the vat isn't blocked

<msavoritias>sounds good. i have some other plans for the db anyway to make it "image" based. so ideally i only want to pass a commit and that is it. so the transactions would be conceptually simple

<msavoritias>i hope at least

IRC channel logs

2024-11-13.log