[WASM] Enable passing tests

This commit is contained in:
Igor Yakovlev
2022-09-10 16:09:47 +02:00
committed by teamcity
parent dbfd20ec4e
commit 38dd68f1f4
6 changed files with 0 additions and 22 deletions
@@ -1,8 +1,3 @@
// IGNORE_BACKEND: WASM
// WASM_MUTE_REASON: BRIDGE_ISSUES
// Before we implemented native wasm strings this passed by chance, only because we inserted unbox intrinsic at the end of
// the BImpl::<get-result>. Need to find common source of this bridge problems.
interface A {
val result: Any
}
@@ -1,8 +1,3 @@
// IGNORE_BACKEND: WASM
// WASM_MUTE_REASON: FAKE_OVERRIDE_ISSUES
// On wasm this will produce conflicting return types, A.g will return Any but we will try to interpret it as String.
// Before wasm native strings this worked by chance because we added unbox intrinsic for strings.
interface I<T> {
val prop: T
@@ -1,8 +1,3 @@
// IGNORE_BACKEND: WASM
// WASM_MUTE_REASON: FAKE_OVERRIDE_ISSUES
// On wasm this will produce conflicting return types, A.g will return Any but we will try to interpret it as String.
// Before wasm native strings this worked by chance because we added unbox intrinsic for strings.
interface I<T> {
val prop: T
@@ -1,8 +1,3 @@
// IGNORE_BACKEND: WASM
// WASM_MUTE_REASON: FAKE_OVERRIDE_ISSUES
// On wasm this will produce conflicting return types, A.g will return Any but we will try to interpret it as String.
// Before wasm native strings this worked by chance because we added unbox intrinsic for strings.
interface I<T> {
val prop: T
@@ -1,4 +1,3 @@
// IGNORE_BACKEND: WASM
// JVM_TARGET: 1.8
// WITH_STDLIB
// FILE: 1.kt
@@ -1,4 +1,3 @@
// IGNORE_BACKEND: WASM
// JVM_TARGET: 1.8
// WITH_STDLIB
// FILE: 1.kt