Mikhail Glukhikh
3fbb7bc920
This commit is intended to get a more clear diagnostic in case when the type checker creates an inconsistent error type due to some classifier inaccessibility. Before this commit, we reported simply ARGUMENT_TYPE_MISMATCH (see test). Now we report also MISSING_DEPENDENCY_CLASS by analyzing an error type of a qualified expression. #KT-66356 Fixed
18 lines
1.2 KiB
Plaintext
Vendored
18 lines
1.2 KiB
Plaintext
Vendored
/Call.kt:(232,241): error: Cannot access class 'com.result.B'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(253,262): error: Cannot access class 'com.result.B'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(271,280): error: Cannot access class 'com.result.B'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(294,296): error: Cannot access class 'com.result.B'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(316,334): error: Cannot access class 'com.result.Owner.Nested'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(316,334): error: Cannot access class 'com.result.Owner.Nested.VeryNested'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(337,345): error: Cannot access class 'com.result.Owner.Nested'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(346,355): error: Cannot access class 'com.result.Owner.Nested.VeryNested'. Check your module classpath for missing or conflicting dependencies.
|
|
|
|
/Call.kt:(383,389): error: Unresolved reference 'result'.
|