Yeah I like that approach. If we can support more ...
# tornadofx
t
Yeah I like that approach. If we can support more than one syntax just for intuitiveness' sake that would be ideal. My RxKotlin initiatives are having a similar problem. And I think you helped me with that a few weeks back. Some operators use one parameter syntax, and the rest use another. It is a terrible feeling for an API designer to make that compromise. Using an API "should just flow" intuitively as you type.