d07f3a14e6
In this test, both frontends resolve to fun Semaphore. Both work this way because interface/class Semaphore classifiers are clashed (ambiguity) and ignored. K2 reports ambiguity for some similar cases, but constructor resolve still ignores ambiguous classifiers when found. (see FirScope.processConstructorsByName in ConstructorProcessing.kt)