I am still not used to operator and overloading, this article both makes sense and seems to provide a meaningful use case outside of what kotlin already implements, and at the same time to confirm I don't like them as a usable feature.

translate(..)

looks nice, but the moment you add a new function to the

Translate

class it will start to look weird.

val t = Translate(...)
t(..)
t.another()

is it just me?

it’s not just you 🙂 but it’s API design if you craft an API regardless of operators and add stuff it might look weird

Cool to know, but also not readable to me.