A modern programming language that makes developers happier.

kotlinlang

When taking in a `combine` function in Arrow, do we assume that such functions are associative?

we don't really require it, but you'll often get surprising results if not

So in other words, results are "stable" up-to associativity? As in, some methods that are "equivalent" to one another assume associativity, and hence won't be equivalent if you pass a weird function in?
And I guess library updates may change the semantics for non-associative functions (as in, the order of calls may change)

is it safer to assume the function is by default left associative and where applicable provide a form suitable for right-associative combines?