Alexander Udalov
db5e00bcc0
Technically we often can compile code which uses missing classes (as long as nothing is called on them) but it seems better to let the user know something's wrong in their setup before the error manifests itself at runtime. Also the Java compiler does the same #KT-4328 Fixed
10 lines
688 B
Plaintext
Vendored
10 lines
688 B
Plaintext
Vendored
compiler/testData/compileKotlinAgainstCustomBinaries/missingDependencySimple/source.kt:7:7: error: cannot access class 'a.A'. Check your module classpath for missing or conflicting dependencies
|
|
b.foo()
|
|
^
|
|
compiler/testData/compileKotlinAgainstCustomBinaries/missingDependencySimple/source.kt:10:21: error: type mismatch: inferred type is A but String was expected
|
|
val x: String = b.foo()
|
|
^
|
|
compiler/testData/compileKotlinAgainstCustomBinaries/missingDependencySimple/source.kt:10:23: error: cannot access class 'a.A'. Check your module classpath for missing or conflicting dependencies
|
|
val x: String = b.foo()
|
|
^
|
|
COMPILATION_ERROR |