Files
Alexander Udalov 55f9f74d5c Tests: do not report backend diagnostics if there's frontend error
In most affected tests, the backend diagnostic such as "conflicting JVM
signature" or "accidental override" is directly caused by some already
existing error reported by frontend, so it doesn't make sense to check
backend diagnostics there.

Tests where that was not the case were moved/copied to
`testsWithJvmBackend`.
2024-03-13 08:38:15 +00:00

55 lines
998 B
Kotlin
Vendored

// !DIAGNOSTICS: -UNUSED_PARAMETER -INAPPLICABLE_JVM_NAME
// WITH_STDLIB
<!CONFLICTING_JVM_DECLARATIONS!>@JvmName("bar")
fun foo(a: Any) {}<!>
<!CONFLICTING_JVM_DECLARATIONS!>fun bar(a: Any) {}<!>
class C {
<!CONFLICTING_JVM_DECLARATIONS!>@JvmName("foo1")
fun foo(list: List<Int>) {}<!>
<!CONFLICTING_JVM_DECLARATIONS!>@JvmName("foo1")
fun foo(list: List<String>) {}<!>
}
// Conflicts in inheritance.
// A1 -> B1 with accidental override
open class A1 {
@JvmName("bar")
open fun foo() {}
}
class B1 : A1() {
<!ACCIDENTAL_OVERRIDE!>fun bar() {}<!>
}
// A2 -> B2 with intended override and conflicting JVM declarations
open class A2 {
@JvmName("bar")
open fun foo() {}
}
class B2 : A2() {
override fun foo() {}
<!ACCIDENTAL_OVERRIDE!>fun bar() {}<!>
}
// A3 -> B3 -> C3 with accidental override
open class A3 {
@JvmName("bar")
open fun foo() {}
}
open class B3: A3() {
}
class C3: B3() {
<!ACCIDENTAL_OVERRIDE!>fun bar() {}<!>
}