The github issue number autocomplete has gone from mostly useless to quite glitchy for me.

Edit: that tweak compares apples and oranges.

What is the behavior when the other method is from a superclass from the class path? Is its name also simple.

Is this just to defend against people using identifiers with dollars that happen to collide? Maybe this is too expensive to support, as it expensive in the happy path. Is it OK because name.toString is computed just once and is required eventually anyway? In that case, it should compare toString and not toSimpleName. (The hypothesis was that preferring comparisons with simple names would be cheaper on average, but that is untested. That is,toSimpleName is a no-op for simple names.)

The CBa error is theizumi-reflect example. The double definition is detected now.