Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
neotypes.Async implicit imports cause divergent implicits
See original GitHub issueI have code that uses cats-effect with higher-kinded types in most of my functions. Here’s an example that should compile fine using the cats.effect.Async typeclass:
import cats.implicits._
import cats.effect._
def flatMapF[F[_]: Async](f: F[Any]): F[Unit] = f.flatMap(_ => Async[F].unit)
This code compiles and works fine unless I import the implicits for neotypes.Async by importing neotypes.implicits.all._ or neotypes.implicits.syntax.all._. The code fails to compile due to a divergent implicit leading the compiler to not know which flatMap method to call.
Currently using the latest snapshot build from master, built locally (0.9.1-SNAPSHOT).
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Is there any place in user land where
mapandflatMapmight be used forneotypes.Async[F]? If not I think it should be better to hide this from the public API.@sloshy @BalmungSan wow that’s amazing exploration and brainstorm!
@BalmungSan I support the approach with making it private. I’m going to complete and merge #34 tomorrow