azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix JvmFieldInInterfaceCompanion.kt for language version 1.4

Browse Source 
Since 1.4, constant value is no longer written to the class file (and
thus cannot be read) for non-const properties. But in sources,
corresponding property descriptors still have the initializer which is
rendered to text. Therefore we disable the source-vs-binary check and
update the test data to check the new behavior.
This commit is contained in:
Alexander Udalov
2020-01-17 20:35:46 +01:00
parent 482874fdc1
commit 3c4e5d7615
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
compiler/testData/loadJava/compiledKotlinWithStdlib/annotations/JvmFieldInInterfaceCompanion.kt
Vendored
+1 -1
View File
@@ -1,4 +1,4 @@
// IGNORE_BACKEND: JVM_IR // NO_CHECK_SOURCE_VS_BINARY
package test package test
compiler/testData/loadJava/compiledKotlinWithStdlib/annotations/JvmFieldInInterfaceCompanion.txt
Vendored
+2 -2
View File
@@ -4,9 +4,9 @@ public interface I {
public companion object Companion { public companion object Companion {
/*primary*/ private constructor Companion() /*primary*/ private constructor Companion()
@field:kotlin.jvm.JvmField public final val x: kotlin.String = "x" @field:kotlin.jvm.JvmField public final val x: kotlin.String
public final fun <get-x>(): kotlin.String public final fun <get-x>(): kotlin.String
@field:kotlin.jvm.JvmField public final val y: kotlin.String = "y" @field:kotlin.jvm.JvmField public final val y: kotlin.String
public final fun <get-y>(): kotlin.String public final fun <get-y>(): kotlin.String
} }
} }