emixa-d

>The biggest downside of this change is that it breaks the handler interface > as it's just passed a single argument, rather than two, I'm not sure how to >...

‘bug’, because Guile should also use a different dynamic-wind (see: ).

>It might be useful to add something like a condition that can hold arbitrary >values. I'll call this a promise for the moment and it might expose >something like this:...

>(for RPC stuff, you can send (query . setter) to the remote channel inside a spawn-fiber for asyncness). Also, you need to wrap 'setter' in a weak reference to make...

That code is broken in the first place -- the async from system-async-mark can be run inside _another_ fiber (or even not in a fiber at all, e.g. Fiber's scheduling...

> (system-async-mark > (lambda () > (put-message ch 'hello) > (abort-to-prompt prompt)) th) I did not notice the `th` here ... That seems much more reasonable. I am, however, quoting...

(Also, pipe trick would be convenient here.)

See, e.g., : > Avoiding signal handling > ● Anything substantial should not be done in a signal handler > ● How can we handle signals, then? > ● The...

No. This is incompatible with ‘move->fdes’ and friends, as it is possible for a different thread to adjust the file descriptor of the port between 'port-read-wait-fd' and ‘select'. (Yes, Fibers...

> [...] and they aren't even implemented as something on top of file descriptors. (They aren't implemented at all yet, but that's a separate issue.)