Slowly coming to the conclusion that named arguments are a good thing. Contrast: Either.cond(foo, bar, baz) With: Either.cond( test = foo, right = bar, left = baz )
Show this thread
-
def cond[A, B](test: Boolean, right: => B, left: => A): Either[A, B] Both can be argued: * always put the happy path first * left goes on the left, silly Which is why I can never remember it :)
I agree, though Either isn't ordered that way. For no better reason than the two words (with different meanings) "right" and "right", happening to be spelled the same way, we decided to put the unhappy outcome first in Either.
-
-
And consequently, higher-order unification works the way it does.
-
Did we? I assumed we copied Haskell's practice. And in Haskell what came first: punning on Right=right or using Right for higher-order unification?
- Show replies
New conversation -
-
-
Huh, I'd habitually use negation with if/then/else to put the unhappy first, so the short-circuit path is lexically shorter in nested code.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.