@puffnfresh @mergeconflict @djspiewak @jsuereth @marius It has also been suggested to model Try with haskell to highlight the bugs.
-
-
Replying to @dibblego
@dibblego@puffnfresh@mergeconflict@djspiewak@marius using that logic, try/catch in scala is broken since it's not hidden in IO.5 replies 0 retweets 0 likes -
Replying to @jsuereth
@jsuereth@puffnfresh@mergeconflict@djspiewak@marius. ...you have something far less useful than you thought you did.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@mergeconflict@djspiewak I doubt that's true. You may be over emphasizing my own opinion here.3 replies 0 retweets 0 likes -
Replying to @jsuereth
@jsuereth@puffnfresh@mergeconflict@djspiewak you say "exception is in IO", you say something we all know that we know. It is irrelevant.2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@mergeconflict@djspiewak to be fair, I think this is an odd ant to squash in a quest to add IO to scala std lib.2 replies 0 retweets 0 likes -
Replying to @jsuereth
@jsuereth@puffnfresh@mergeconflict@djspiewak sure, IO is good, but even without it, you can do what what Try attempts without the bugs.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@mergeconflict@djspiewak By staging computation? Sure, let's see a pull request.1 reply 0 retweets 0 likes -
Replying to @jsuereth
@jsuereth@puffnfresh@mergeconflict@djspiewak I missed context here. Please clarify. PS I suck balls at twitter.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@puffnfresh@mergeconflict@djspiewak "do what try attempts without bugs". Because Java-interop exists, any method can throw.2 replies 0 retweets 0 likes
@jsuereth @puffnfresh @mergeconflict @djspiewak Sure, easy, but it's a complete rewrite.
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.