I.e. ```abstract class ReceiverClass { open fun ...

# announcements

[Paul Woitaschek]

I.e.

abstract class ReceiverClass {

 open fun String.onSomethingHappened(){
   println(this)
 }
}

class Child  : ReceiverClass(){

  override fun String.onSomethingHappened() {
    super.onSomethingHappened() <-- doesnt compile
    println("hello world")
  }
}

[Stephan Schroeder]

does the code compile without the super.onSomethingHappened?? I'm very much surprised that you seem to be able to override functions with receivers at all, since my mental model for them is that it's basically syntactic sugar for static methods.

[Paul Woitaschek]

Sure why not

[Paul Woitaschek]

Its not synthetic sugar for static methods its synthetic sugar to have a receiver 🙂

[Paul Woitaschek]

I use it on android with viewBinding

[Paul Woitaschek]

So I have an open B.onBindingCreated() function and all my rendering functions have the binding as a receiver

[Kroppeb]

super.onSomethingHappend() would make the super the receiver instead of the String. We still don't have a way to do multiple receivers.

[Kroppeb]

I found this workaround

Untitled