Adam Fraser
Adam Fraser
Understood. It is more an issue for contributors and readers of the code.
Yes, the downside of the laws framework is that you need a different instance for each kind since we don't really have a way to abstract over kindedness in Scala...
I spent some time playing with this: ```scala package zio.prelude.fx trait ComposeState[S1, S2, S3, S4] { type In type Out def compose(left: S1 => S2, right: S3 => S4): In...
The main issue I ran into is the interaction between this and the variance on `ZPure`. To use this in composition operators on `ZPure` we really want `ComposeState` and `Aux`...
I think if we went with my proposal in #424 we wouldn't need this because `None` would represent there not being any "successful" value, which could occur if either the...
@lemastero I think that is fine for testing. I am working on adding an `Enumerable` type class and then you could say that given an `Enumerable[A]` and an `Equal[B]` you...
@sideeffffect Yes! Sorry about that! Just commented.
Sounds good.
@thesamet Yes, we found that an `Inverse` operation that was the inverse of the normal associative operation and "undid" it was more general because you can describe for example subtraction...
Yes you are definitely right that there are operations that are commutative but not associative. In an earlier version `Commutative` actually didn't extend `Associative`. Our perspective was that there are...