Merge together MultiplatformHighlighting and MultiplatformAnalysis tests
Basically, the former uses an old quickly-scrapped infrastructure, which were not applicable for HMPP, so the latter tests were written. So, both check for one and the same thing (highlighting in MPP projects), but MultiplatformAnalysisTest is more modern, and has a lot of inconvenient stuff in MultiplatformHighlighting fixed ^KT-43116 Fixed
This commit is contained in:
@@ -0,0 +1,4 @@
|
||||
package sample
|
||||
fun common(): Boolean {
|
||||
return <!TYPE_MISMATCH!>""<!>
|
||||
}
|
||||
@@ -0,0 +1,7 @@
|
||||
MODULE common { platform=[JVM, JS, Native] }
|
||||
MODULE jvm { platform=[JVM] }
|
||||
MODULE js { platform=[JS] }
|
||||
|
||||
common -> STDLIB_COMMON { kind=DEPENDENCY }
|
||||
jvm -> common { kind=DEPENDS_ON }
|
||||
js -> common { kind=DEPENDS_ON }
|
||||
@@ -0,0 +1,5 @@
|
||||
package sample
|
||||
|
||||
fun js() {
|
||||
println(common())
|
||||
}
|
||||
@@ -0,0 +1,6 @@
|
||||
package sample
|
||||
|
||||
fun jvm() {
|
||||
println(common())
|
||||
println(<!UNRESOLVED_REFERENCE!>js<!>())
|
||||
}
|
||||
Reference in New Issue
Block a user