Revamp `Subscription`, `Stream` APIs to make combinators easy about effection HOT 4 CLOSED

This sounds like a nice simplification.

from effection.

The one difficulty is that it is annoying to have to save the back reference to Subscription when creating it by hand:

let subscription = {
  *next() {
     // implement next
  },
  *[Symbol.iterator]() { return subscription; },
};
return subscription;

Perhaps we can make a helper "createSubscription()" that helps you do it my just accepting the content of next:

createSubscription(function* next() {
  // implementation of next operation.
});

So for example, the implementation of Subscription in Channel would be something like:

subscription: createSubscription(function* next() {
  let message = items.pop();
  if (message) {
    return message;
  } else {
    return yield* action<Item>(function* (resolve) {
       consumers.unshift(resolve);
    });
  }
}),

Thus far, it has been extremely rare to create subscriptions by hand, since most of the time, I just end up using Channel for lower level ops.

from effection.

I'm going to advocate that we first disambiguate streams from subscriptions (you should never need to deal with a subscription directly) and then we can add make subscriptions streamable individually which will be possible if they have separate API.

from effection.

Closed by #696

from effection.