I agree completely, unfortunate we are too late… Changing this would mean a breaking change…
So to support the strategy pattern, another syntax is needed.
There are several issues related to this problem, under which 3 are listed here:
(I saw that the strategy-pattern was only half implemented after the kotlin - puzzlers:https://github.com/angryziber/kotlin-puzzlers/blob/master/src/delegates/map/mapped-property-delegate.kts)
By the way, the reason why is chosen for the half strategy pattern:
For the this, you need to give the classes a object, with the this as reference…
The accessed fields/methods can in those cases not be private or protected.
The problem is of course that the interfaces can be used for stand - alone classes…
Having said that, I think the strategy pattern in Kotlin is still easier to write than in Java 