Iurii Vyshnevskyi

Neither it works on desktop Safari. While it works fine in chrome based browsers like Edge (in desktop as well).

> > @connor4312 @tanhakabir seems like this might be the Safari issue we were discussing? > > I don't think so. I tried on safari, chrome and edge, and on...

> If you throw `transparent inline` in the works you may get a different response. Tanks, changing `fff2` signature to `transparent inline` does solve my problem. The custom error message...

So, `summonInline[Test[Test1]]` in object `Main` is inlined during the typer phase, that is why when `Typer.adapt` is called from `Implicits.typedImplicit` for the `given_Test_A` instance - it is not inlined. But...

It seems that `transparent inline given` is also not working as expected. If we add another inline given instance for Test with exactly the same signature, but that would not...

> > Then calls to `fff1[Test1]` and `fff1[Test2]` and top level `summonInline[Test1]` and `summonInline[Test2]` would give an "Ambiguous given instances" errors in both cases, no matter whether `transparent ` is...

> Maybe related to your inquiry #12429 Agree. Looks like this is the behavior that is described now in the documentation section I referenced.

I'll summarise how I see the problem now. - the compiler considers all available given candidates when `summonInline` is encountered using usual precedence rules - candidates for inlining are type...