Closed mielientiev closed 5 years ago
This a bug caused by the two methods at the same trait and thus priority. https://github.com/typelevel/cats/blob/master/core/src/main/scala/cats/data/Kleisli.scala#L294-L299
Looks like we can move either up or down. So we will have to insert a new trait into the chain
to reduce BC change maybe name it KleisliInstances4a
?
We can place this new trait in between KleisliInstances4
and KleisliInstances5
and move one of the instances, say catsDataApplicativeErrorForKleisli
to it, and to avoid a mima exception we can leave the original one but make it non-implicit.
On it 👍
I see the next error in 1.4.0 and 1.5.0-RC0 cats: