Scaladoc documents "implicitly added" methods which are shadowed

[Sporarum]

Example, method == in Int:
https://scala-lang.org/api/3.x/scala/Int.html#

What seems to be happening:

In the case where:

• type A defines a method f
• type B defines a method f of same signature
• there is an implicit conversion from A to B

Method f is documented twice in A, even though B's can never be called

Expectation

Only methods which are actually callable should be displayed

Or if we want to keep this information somewhere, there should be a section at the very end grouping all of these, like "Implicitly added, but shadowed by explicit members", potentially folded by default

[Sporarum]

I said of the same signature, but we could refine it further if we wanted, I believe the actual condition would be something like:

There exists no arguments such that A.f is not applicable to them, but B.f is

Or

There are no arguments such that B.f is more specific than A.f

Depending on wether we search for implicit conversion only if there are no applicable overrides or not

[som-snytt]

This may be #15853 ? I don't remember the details, but it rang a bell.

[Sporarum]

They seem very similar but slightly different, I believe my proposed solutions above would solve both ?