I wish Kotlin had support for custom operators like F# lol.

# compose

[dewildte]

I wish Kotlin had support for custom operators like F# lol.

[Robert Menke]

What are you looking for beyond infix functions?

[alexsullivan114]

It's cool being able to have custom operators that support monad transformations. Or I guess at least flatMap

[alexsullivan114]

I'm not sure it's worth the headache but ReactiveSwift and libraries like that build up a pretty ergonomic API for making reactive calls by using things like ~= to bind disposables and whatnot

[dewildte]

I built my own parser combinator library in Kotlin and using infix functions like _AND _AND_ AND_ vs .>> .>>. >>. is not as nice and can get verbose.

[dewildte]

For example <?> takes a parser and modifies its error messages but _?_ is not valid Kotlin.

[dewildte]

_em_ is fine I guess but I like to stick to common conventions.

[Pablichjenkov]

I wish I could understand hieroglyph 🗿

[spierce7]

I actually think it encourages the creation of nonsense APIs. for libs, leading to less discoverable libraries i.e. you can’t google for documentation on the scala ++=- function. And even if you could, isn’t a function that imparts some semblance of what it does actually better? With a lot of this stuff, less is more.

[themishkun]

@spierce7 When you stumble across this function first time, maybe it looks mystical. But when it is a part of a library with nice algebraic design you start writing this as a breeze. My suggestion would be to always provide some kind of real name and apply custom operator only via some kind of annotation