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
This commit is contained in:
+5
@@ -215,6 +215,11 @@ public class BytecodeListingTestGenerated extends AbstractBytecodeListingTest {
|
||||
runTest("compiler/testData/codegen/bytecodeListing/annotations/JvmSynthetic.kt");
|
||||
}
|
||||
|
||||
@TestMetadata("kt27895.kt")
|
||||
public void testKt27895() throws Exception {
|
||||
runTest("compiler/testData/codegen/bytecodeListing/annotations/kt27895.kt");
|
||||
}
|
||||
|
||||
@TestMetadata("kt9320.kt")
|
||||
public void testKt9320() throws Exception {
|
||||
runTest("compiler/testData/codegen/bytecodeListing/annotations/kt9320.kt");
|
||||
|
||||
Reference in New Issue
Block a user