Johannes Neubauer

> As the proposal is going to change the overload resolution, the indented behavior of overload resolution should be described in the proposal. > > I'll clarify the terms, so...

> Ah now I know what you mean. If the scope for available symbols could be declaration-site that would be great, because then I could call stuff in an inline...

> Could you explain, what should happen next? It should happen exactly the same as if I had written this without an inline function: ``` kotlin // see above... fun...

> That's where things become seeming weird: thus to use such an inline function one has to know how its inner workings, its source, otherwise coping with such errors is...

At runtime?

So the information should be there to produce the compiler error and to do the "downcast", shouldn't it? For the inlining at compile time you need the source code :smile:...

Sorry this is a bit off-topic, but I tried this code fiddling around with the example of @ilya-g: ``` kotlin // inline function declaration-site interface A fun A.foo() { print("a")...

@groostav > If dynamic makes it into the Java-side of kotlin, then you might be able to get your polymorphic extension functions with a ~simple~ > [...] > Still, I'm...

@ilya-g I will then update the proposal according to our discussion and add this example, ok? But this may take a day or two, since I'm low on (spare) time...

> The result of the expression `C() as B` is an instance of type `B`: we want to call foo on a `B`. There is no vtable entry for foo...