Alexey Sedunov 84c6f9bf45 Create from Usage: Fix choosing superclass for abstract member ...

This applies to cases when non-existing member is called without
explicit receiver

 #KT-21332 Fixed

2017-11-30 12:49:25 +03:00

..

classNoExplicitReceiver.kt

…

classNoExplicitReceiver.kt.after

…

explicitReceiverOfContainingClass.kt

Create from Usage: Support generation of abstract members for superclasses. Skip non-abstract superclasses when generating abstract member

2016-12-02 14:14:05 +03:00

explicitReceiverOfContainingClass.kt.after

Create from Usage: Support generation of abstract members for superclasses. Skip non-abstract superclasses when generating abstract member

2016-12-02 14:14:05 +03:00

inAbstractSuperclass.kt

Create from Usage: Fix choosing superclass for abstract member

2017-11-30 12:49:25 +03:00

inAbstractSuperclass.kt.after

Create from Usage: Fix choosing superclass for abstract member

2017-11-30 12:49:25 +03:00

inBaseInterface.kt

Create from Usage: Fix choosing superclass for abstract member

2017-11-30 12:49:25 +03:00

inBaseInterface.kt.after

Create from Usage: Fix choosing superclass for abstract member

2017-11-30 12:49:25 +03:00

interfaceNoExplicitReceiver.kt

…

interfaceNoExplicitReceiver.kt.after

…

noAbstractSuperclass.kt

Create from Usage: Fix choosing superclass for abstract member

2017-11-30 12:49:25 +03:00

notAbstractClass.kt

Introduce "use expression body" inspection #KT-16063 Fixed

2017-07-07 18:15:06 +03:00

otherExplicitReceiver.kt

Introduce "use expression body" inspection #KT-16063 Fixed

2017-07-07 18:15:06 +03:00