[FE] Prohibit expect fun interface to have non-fun actual counterpart
In K1 .isFun is always false for Java classes, so extra check is added for that. This is not needed for K2, because .isFun is true for all Java classes. Here it is not necessary to check that interface has only one method, because such check will be done in the place where interface implementation is created. ^KT-39362 Fixed
This commit is contained in:
committed by
Space Team
parent
59d126abc5
commit
456d3e0f42
@@ -19,3 +19,11 @@ expect class C4<F>
|
||||
|
||||
|
||||
expect abstract class ExtendsNumber : Number
|
||||
|
||||
expect fun interface FunInterface {
|
||||
fun run()
|
||||
}
|
||||
|
||||
expect fun interface FunInterface2 {
|
||||
fun run()
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user