News for hackers. Stuff that matters.
Re:Dependently Typed Programming by seanmcdirmid on Tuesday July 01, 2014 @07:27PM (#7974124)
> If figuring out what happened when something failed is complicated because there were several maybe monads and in the end you got nothing, then Haskell solves this very nicely if I'm not mistaken: there's "Either", which can carry an error message along with the fact that there's no result.

Does that really work? Say you have an error in a long pipeline, wouldn't "Either" cause processing down the line to treat the error as valid data (the error wouldn't be None)?

What you really want is a maybe monad where you can propagate wither a Valid answer or an Error condition, where operations on the value merely propagate the error condition. Also, it would be nice if the monad was integrated into a debugger so the error condition could carry along enough context to allow the user to jump to execution context where the error occurred during debugging (if we are talking about programmatic errors, a distinction must be made between errors of programming vs. exceptions from the environment that can/should be handled).

Re:Dependently Typed Programming by chriswarbo on Tuesday July 01, 2014 @07:31PM (#7974142)
If the pipeline is constructed with fmap, <*> or >>= then the pipeline's constituents will only be applied to Right values. An error (a Left value) will short-circuit the pipeline and be returned as-is.

Alternatively, we could be more fancy and branch such that errors received their own, separate, processing (eg. logging).

Re:Dependently Typed Programming by seanmcdirmid on Tuesday July 01, 2014 @07:39PM (#7974182)
Cool. One of the advantages of null pointer exceptions is that you can break into the debugger when they happen. Masking them and continuing is absolutely what you don't want to do.
Re:Dependently Typed Programming by tel on Tuesday July 01, 2014 @09:32PM (#7974587)
Either tends to be used for error conditions that arise from the outside—after all, you are (a) explicitly denoting them and (b) presumably handling them. Programmer errors tend to arise in invariant violations. Sometimes these are marked with `error "cannot occur"` or silly things like that. Dropping into a debugger here would be tremendous.
Re:Dependently Typed Programming by dllthomas on Wednesday July 02, 2014 @09:42AM (#7976879)
A simple, standard equivalent of __FILE__ and __LINE__ would be 60% as useful as a debugger.
Re:Dependently Typed Programming by tel on Wednesday July 02, 2014 @01:28PM (#7978274)
Agreed, at least in mostly pure code. Lennart proposed one on his blog but I don't think it got far.

For IO heavy stuff I think a debugger would still be valuable.