1f989dce64
This commit covers enum entry vs companion member case, when two companion objects are in the scope. K1 reports UNRESOLVED_REFERENCE here, probably due to ambiguity. About K2, while resolving Some.foo it first tries to resolve Some as a "general" variable access, and gets two candidates with companions. After that it tries to resolve Some as a qualifier, but we have no scope with a single qualifier, so no influence here. With two ambiguous candidates with companions for Some, OVERLOAD_RESOLUTION_AMBIGUITY is reported.