- 02 12月, 2020 7 次提交
-
-
由 Ilmir Usmanov 提交于
but not for value classes. Since inline classes and value classes share the same flag, we use presence of the annotation to distinguish them.
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
Also add ABI tests for @JvmStatic/JvmOverloads + 'external'.
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
-
- 01 12月, 2020 12 次提交
-
-
由 Georgy Bronnikov 提交于
-
由 Georgy Bronnikov 提交于
-
由 Dmitriy Novozhilov 提交于
-
由 Mikhail Glukhikh 提交于
#KT-43342 Fixed
-
由 Ilya Goncharov 提交于
^KT-43668 fixed
-
由 Alexander Udalov 提交于
References to properties with JvmStatic getter were not handled in MakeCallsStatic (by overwriting dispatchReceiver with null) because the property itself was not considered static. #KT-43672 Fixed
-
由 Georgy Bronnikov 提交于
The old test sequence failed for toplevel functions because of file class wrappers, so that the second branch was never invoked.
-
由 Roman Golyshev 提交于
-
由 Roman Golyshev 提交于
Some of those tests are failing in the FIR IDE
-
由 Alexander Udalov 提交于
-
由 Alexander Udalov 提交于
... in case `-Xno-optimized-callable-references` is enabled. Before this change, the generated abstract equals/hashCode methods were considered as accidental overrides because they did not have equals/hashCode from the supertype in the overriddenSymbols list. #KT-43666 Fixed
-
由 pyos 提交于
1. When an annotation has multiple targets, the priority goes like this: constructor parameter (if applicable) -> property -> backing field. 2. The argument to `kotlin.annotation.Target` is a vararg, so that should be handled as well. 3. `AnnotationTarget.VALUE_PARAMETER` allows receivers, constructor parameters, and setter parameters, while `AnnotationTarget.FIELD` allows both backing fields and delegates. Known issue: java.lang.annotation.Target is not remapped to the Kotlin equivalent, so things are still broken for pure Java annotations.
-
- 30 11月, 2020 21 次提交
-
-
由 Andrei Klunnyi 提交于
Android gradle-project model differs from what we have for pure Java and MPP. It's the reason why application classpath cannot be collected correctly. Until universal solution is provided delegation to gradle is put under the registry flag. If disable platform runner is used as before.
-
由 Ilya Goncharov 提交于
^KT-42357 fixed
-
由 Ilya Goncharov 提交于
[JS IR] Nullize external empty varargs [JS IR] Concat varargs with array of nonVarargs arguments ^KT-42357 fixed
-
由 Ilya Goncharov 提交于
[JS IR] Add tests with empty vararg and default arg before it [JS IR] Ignore backend in tests instead of target backend [JS IR] Add function with named spread operator [JS IR] Remove ignoring of current js backend in jsExternalVarargFun [JS IR] Add with arguments after vararg ^KT-42357 fixed
-
由 Ilya Goncharov 提交于
^KT-43668 fixed
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
-
由 Dmitry Petrov 提交于
-
由 Dmitriy Novozhilov 提交于
[TEST] Inherit `UpdateConfigurationQuickFixTest` from `KotlinLightPlatformCodeInsightFixtureTestCase` This is needed for proper test muting
-
由 Alexander Udalov 提交于
-
由 Alexander Udalov 提交于
-
由 Mikhael Bogdanov 提交于
-
由 Dmitriy Novozhilov 提交于
Those tests are failing only on windows agents after switch to 202 platform
-
由 pyos 提交于
Non-const properties may need them too with if the 1.4 feature NoConstantValueAttributeForNonConstVals is disabled.
-
由 Mikhail Glukhikh 提交于
-
由 Mikhail Glukhikh 提交于
#KT-43584 Fixed
-
由 Mikhail Glukhikh 提交于
-
由 Roman Golyshev 提交于
This reverts commit e127ea3d
-
由 Roman Golyshev 提交于
This reverts commit dba14ba9
-
由 Roman Golyshev 提交于
-