Implicit interfaces as in Go


#21

Interesting. We'll look into it. Thanks!


#22

I know this is an old post, but this would be a great addition to kotlin.
Example code would be almost the whole tornadofx project.
So, any update?


#23

It’s not an easy feature, but it’s still on the table, we did some experiments, but some more would be required before we make a decision


#24

My main problem is that implicit interfaces would only be based upon the functions implemented. Especially for single method interfaces this would mean a good probability of name collisions as there is no namespacing in function names themselves.