Define a zero-boilerplate generic carrier about fused-effects HOT 8 CLOSED

Same as #133, we’re under PVP rather than semver. So 0.3.1 would be a minor release.

If we run out of minor release numbers we can run to the number store and order some more!

😂

from fused-effects.

@joshvera indicated he was on board with this.

@joshvera @patrickt: What do we think about doing this for the 0.3 release vs. pushing it to a minor version (e.g. 0.3.1)?

from fused-effects.

I’m super curious whether we can implement something analogous which carries state along with it.

from fused-effects.

If we do this, we should also benchmark runInterpret for an effect like State against a carrier like StateC.

from fused-effects.

What do we think about doing this for the 0.3 release vs. pushing it to a minor version (e.g. 0.3.1)?

I'm partial to a 0.3 minor release as per semver. I believe semver would consider a 0.3.1 a patch release. If we run out of minor release numbers we can run to the number store and order some more!

from fused-effects.

After discussion w/ @joshvera, we’ve decided to ship this in 0.3.1 rather than holding up 0.3 waiting on it.

from fused-effects.

This looks super similar to my effect type

newtype Semantic r a = Semantic
  { runSemantic
        :: ∀ m
         . Monad m
        => (∀ x. Union r (Semantic r) x -> m x)
        -> m a
  }

If it works, this I think would be the stepping stone between our effects implementations. You guys might be putting me out of business here!

from fused-effects.

The trick for doing statefulness is to just let m be StateT s n

from fused-effects.