Jonathan Reem
Jonathan Reem
I've pushed another commit adding a `BufferedTransportServer` wrapper which causes the yielded `Transport`s to be wrapped in a `BufStream`. I think it makes sense to provide this as part of...
We _may_ even want to integrate `BufStream` into the impl of `TransportServer` for `TcpListener` so the simple thing (passing a `TcpListener` as your `TransportServer`) does the right thing.
Ok, I can change it back.
Another case where `run` would be useful: Let's say we have some function like this: ``` export function* doBackground(saga, config) { const handle = yield fork(backgroundTask(saga, config)); return handle; }...
Any thoughts here? Really all this issue is asking for is the `run` effect. Does anyone have thoughts on how difficult this would be to implement? I would be happy...
`run` does the same thing as `call` except that if the saga it runs forks, the forks are attached to the saga that yielded the `run` effect, not the sub-saga....
`calling` will never be resumed because a `call` effect only ends when all the sagas forks end.
It looks like it is covered here https://redux-saga.github.io/redux-saga/docs/advanced/ForkModel.html.
So originally I phrased this all in Monad language because I thought it would be helpful to have some context to refer to, but it seems to have caused more...
A Monad is just a type that fulfills a few criteria, mainly that there exists a set of functions `pure` and `bind` which operate on the type and whose implementation...