Dear #scala I wrote scala.Either in 2008. I wrote scalaz.\/ in 2013. Please stop using scala.Either. There are reasons.
-
@dibblego And I wrote org.scalautils.Or in 2013, to show we can have both good types *and* good names in#scala http://www.scalautils.org/user_guide/OrAndEvery …
@bvenners Identifier name reasoning is morally obnoxious and I will not be a part of it. http://dl.dropbox.com/u/7810909/media/doc/parametricity.pdf …
-
-
@dibblego How about identifier name *remembering*? Can't "relevant" names help people remember meaning once they understand the types? -
@bvenners Yes and \/ is quite well established to denote logical disjunction. - Show replies
New conversation -
-
-
@dibblego big fan of those slides. noticed in this reading tho...`thisIsNotReverse a = a` or `thisIsNotReverse = []` meets both specs no? -
@_jrwest pretty sure it breaks the third. - Show replies
New conversation -
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.