News for hackers. Stuff that matters.
Re:Becoming Productive in Haskell by tel on Friday April 24, 2015 @08:22AM (#9432777)
I've personally found it very easy to handle "exceptions" in Haskell. Partial answers feel "bad" in Haskell because all the core functionality is clean enough to not need them, but on the other hand that makes for some of the best tools around for dealing with partiality.
Re:Becoming Productive in Haskell by JadeNB on Friday April 24, 2015 @02:44PM (#9435276)
> Partial answers feel "bad" in Haskell because all the core functionality is clean enough to not need them

Not to need them, sure, but not not to use them. (I swear that's the right number of 'not's.) I don't understand why something like Neil Mitchell's `Safe` isn't just the way that things are done by default.

Re:Becoming Productive in Haskell by tel on Friday April 24, 2015 @03:47PM (#9435621)
Ugh, yeah, total agreement here. Historical accident, I suppose. I try to pretend like `head` and `tail` just don't exist.

You can always recognize a file where I'm doing list ops because I define `uncons :: [a] -> Maybe (a, [a])` at the top of the file, haha.

Re:Becoming Productive in Haskell by mightybyte on Friday April 24, 2015 @04:33PM (#9435859)
Even better than safe, all this has been consolidated very nicely in the errors package.