is it not possible to use a reference to a field in a companion object without using

.Companion

?

class Foo {
    companion object {
        val bar: Int = 42
    }
}
// Works
val member2 = Foo.Companion::bar
// Doesn't work: unresolved reference
val member = Foo::bar

There's pretty big difference between class member function references (type

KFunction0<R>

) and companion function references (type

KFunction1<Foo, R>

), maybe that's why it's not allowed.

You could have a bar function on Foo class and in companion. How would compiler know which one? For that matter, how would you? Kotlin favours explicit definitions anyway.

true, but java in that situation just errors on the ambiguity

Or they intentionally show explicit mess over implicit?

I guess you’ll need Companion classifies if inside of it

what do you mean?

Foo::bar corresponds Foo#bar which is instance property Foo::Companion::bar corresponds Foo.Companion#bar which is Companion’s property I guess Kotlin requires write Companion if it is in Companion?

ah, yeah that's what i found...was just wondering if that was really the case (

.Companion

being required) or if i was missing something

But I think I misreading something — Java doesn’t require it, so Kotlin doesn’t either?

Right, java doesn't...but Kotlin appears to.

But if Kotlin doesn’t, IDEA would give you a hint that unnecessary ‘Companion’ — I believe in builtin Kotlin support works, mmm