Alexander Udalov 17d740a373 Do not try computing return type in OverloadChecker ...

Return type is not needed for checking overloads, but querying it may
involve resolving function bodies, which usually happens after overload
checking (see LazyTopDownAnalyzer.analyzeDeclarations) and at this point
can lead to incorrect BACKING_FIELD_REQUIRED value being computed for
some properties (see KT-27895)

 #KT-27895 Fixed

2018-11-07 11:00:15 +01:00

..

defaultTargets.kt

…

defaultTargets.txt

…

deprecatedJvmOverloads.kt

…

deprecatedJvmOverloads.txt

…

JvmSynthetic.kt

…

JvmSynthetic.txt

…

kt9320.kt

Update testData for restricted expression annotations retention

2018-07-20 10:39:51 +03:00

kt9320.txt

Update testData for restricted expression annotations retention

2018-07-20 10:39:51 +03:00

kt27895.kt

Do not try computing return type in OverloadChecker

2018-11-07 11:00:15 +01:00

kt27895.txt

Do not try computing return type in OverloadChecker

2018-11-07 11:00:15 +01:00

literals.kt

Update testData for restricted expression annotations retention

2018-07-20 10:39:51 +03:00

literals.txt

Update testData for restricted expression annotations retention

2018-07-20 10:39:51 +03:00

noAdditionalAnnotationsInAccessors.kt

Don't generate additional annotations on synthetic accessors

2018-09-14 16:23:57 +02:00

noAdditionalAnnotationsInAccessors.txt

Don't generate additional annotations on synthetic accessors

2018-09-14 16:23:57 +02:00

noAnnotationsInSyntheticAccessors.kt

Don't generate annotations on synthetic accessor parameters

2018-09-19 12:14:09 +02:00

noAnnotationsInSyntheticAccessors.txt

Don't generate annotations on synthetic accessor parameters

2018-09-19 12:14:09 +02:00

onProperties.kt

…

onProperties.txt

…

onReceiver.kt

…

onReceiver.txt

…