chpill
chpill
Okay, I think I was missing the point a bit. Only effects should be exposed with some dispatch functions, as they are the only ones that should be causing side-effects....
Note to self: the `do-fx` interceptor only need to provide the regular `dispatch` function: As the effect handlers are going to be called during a "dispatching" ie when `*handling*` is...
This should be better with https://github.com/chpill/re-frankenstein/commit/c3e28389c840305f1a4686628e1a19c111e08689
I just realized that my comment about synchronous dispatch earlier was in fact mistaken. Many effects will in fact trigger asynchronous behaviors. In that case, it should be possible to...
https://github.com/chpill/re-frankenstein/commit/c3e28389c840305f1a4686628e1a19c111e08689
Note that constant folding only breaks the file produced by advanced compilation. You only need to tell the worker to avoid that particular file. More detail in the issue on...
I made a small PR to illustrate my suggestion https://github.com/tonsky/rum/pull/137/files
Any update on this? For reference, I run into this problem in https://github.com/chpill/re-frankenstein, where I have had to create some workaround mixins to put a the end of the mixin...
> My current thinking is that it's better to keep the guarantees that synchronous, blocking I/O give us. Particularly if Java's virtual threads allow us to park a thread for...
@weavejester thank you for your input! Yes, I'll open an issue in the Ring repository shortly.