<@UE3D4UE15> see if this helps: <https://arrow-kt....

# arrow

[pakoito]

@Bob Glamm see if this helps: https://arrow-kt.io/docs/patterns/dependency_injection/#disambiguating-colliding-instances

[Bob Glamm]

Ok, based on that I think I see the problem:

interface AnalyzerSyntax: Async<F>, JDBCOps<F> { ... }
interface JDBCOps<F>: MonadDefer<F> { ... }

and attempting to create AnalyzerSyntax with evidence via IO.async() while JDBCOps has been created with evidence via IO.monadDefer() means the compiler sees multiple implementations of common typeclass methods via both evidence instances provided. Does that sound about right?

[pakoito]

correct

[pakoito]

now, if it's a compiler warning you can ignore it

[pakoito]

if not, you have to use any of the techniques I mentioned above

[pakoito]

try override + super first

[Bob Glamm]

Well... there are 91 instances of that particular error, so I will look at refactoring based on evidence instances first, I think 🙂

[Bob Glamm]

since IO.async() and IO.monadDefer() apparently share 91 typeclass methods via inheritance

[Bob Glamm]

Thanks for the link, though - that helped immensely