Unrefined Eff type #20
Conversation
|
I like the look of this. Will the eff optimisations fire on this type too? |
src/Control/Monad/Eff/Unrefined.purs
Outdated
|
|
||
| -- | A variant of `Control.Monad.Eff.Eff` without the row of effects. | ||
| -- | | ||
| -- | `Unrefined.Eff a` is isomorphic to `exists eff. Refined.Eff a`. |
There was a problem hiding this comment.
Should this say Refined.Eff eff a?
| derive newtype instance applyEff :: Apply Eff | ||
| derive newtype instance applicativeEff :: Applicative Eff | ||
| derive newtype instance bindEff :: Bind Eff | ||
| derive newtype instance monadEff :: Monad Eff |
There was a problem hiding this comment.
Can we give this type a MonadEff instance?
There was a problem hiding this comment.
I replaced unrefined actually.
I'm not sure. Not directly, but if enough newtype wrappers get removed, it's possible. Edit: no, it looks like we need compiler support since the dictionaries aren't getting inlined. |
|
^ I was going to say, does this need to go in core, since there's already the " |
Well, I'd like to see the dependency inverted and |
I chose not to export constructors so that we can eventually swap around the dependencies (regular
Effimplemented using unrefinedEffplus a phantom row) later, if this proves to be useful.