Scala developers from Java should know about the problems of "Y throws X" vs "Either[X, Y]" - having effects as types works much better!
-
-
Replying to @puffnfresh
@puffnfresh why doesn’t Scala make them the same?1 reply 0 retweets 0 likes -
Replying to @puffnfresh
@puffnfresh … could the compiler have made JVM exceptions appear to be Either’s instead of making the translation the programmer’s job2 replies 0 retweets 0 likes -
Replying to @natpryce
@natpryce@puffnfresh Possibly could now, Either came relatively recently to Scala.1 reply 0 retweets 0 likes -
Replying to @tomjadams
@tomjadams@natpryce@puffnfresh that's the purpose of Try, which is analogous to either with Throwable on the left and some catching kit1 reply 0 retweets 0 likes -
Replying to @jedws
@jedws@tomjadams@natpryce@puffnfresh Try is a bit silly, imho. Scala just needed a right biased either like https://github.com/scalaz/scalaz/blob/scalaz-seven/core/src/main/scala/scalaz/Either.scala#L395 …3 replies 0 retweets 0 likes -
Replying to @benkolera
@benkolera@jedws@natpryce@puffnfresh Yes, well, you didn't hear the swearing when@dibblego first got Either into the std lib.2 replies 0 retweets 0 likes
@tomjadams @benkolera @jedws @natpryce @puffnfresh There is talk of doing this in a better JVM language (same for null and side-effects).
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.