News for hackers. Stuff that matters.
Re:The Day Python Embarassed Imperative Programming by icebraining on Monday February 27, 2012 @11:56AM (#3639591)
However, it is not general, e.g. it does not provide a solution if you want to chain computations where returning None/Nothing is valid (e.g. a Map lookup in Haskell).

But I think that's a feature, not a bug. Conflating errors and valid values leads to ambiguity. As PEP 20 says, "Explicit it better than implicit".

If you actually want certain function return values to act as a failure, I think you should wrap it in a new function that adds those semantics.

There are no comments on this comment yet.