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

Standardize and improve descriptions of intentions/inspections

Browse Source
This commit is contained in:
Alexey Belkov
2018-03-10 13:34:20 +03:00
committed by Mikhail Glukhikh
parent bc7ccbc39b
commit 3b2bbee595
276 changed files with 359 additions and 356 deletions
Download Patch File Download Diff File Expand all files Collapse all files
idea/resources/inspectionDescriptions/FakeJvmFieldConstant.html
+7 -7
View File
@@ -1,16 +1,16 @@
<html>
<body>
<p>
This inspection reports non-const Kotlin properties used as Java annotation arguments.
It's possible for property which is annotated by <code>@JvmField</code>,
has initializer that can be evaluated in compile-time, has primitive or String type.
Such properties have ConstantValue attribute in bytecode in Kotlin 1.1-1.2.
This attribute allows javac to fold usages of the corresponding field, and use that field in annotations.
This inspection reports non-<b>const</b> Kotlin properties used as Java annotation arguments.
It is possible for a property which is annotated with <b>@JvmField</b>,
has an initializer that can be evaluated at compile-time, has a primitive or <b>String</b> type.
Such properties have a <b>ConstantValue</b> attribute in bytecode in Kotlin 1.1-1.2.
This attribute allows javac to fold usages of the corresponding field and use that field in annotations.
This can cause incorrect behavior in case of separate or incremental compilation in mixed Java/Kotlin code.
</p>
<p>
This behaviour is subject to change in Kotlin 1.3 (no ConstantValue attribute more).
Recommended action: replace <code>JvmField</code> annotation with <code>const</code> modifier on relevant Kotlin property or inline it.
This behavior is subject to change in Kotlin 1.3 (no <b>ConstantValue</b> attribute any more).
Recommended action: replace the <b>@JvmField</b> annotation with a <b>const</b> modifier on a relevant Kotlin property or inline it.
</p>
</body>