Haskell: The Bad Parts, part 2 (2020)

Re:Haskell: The Bad Parts, part 2 (2020) by jrochkind1 on Tuesday February 09, 2021 @01:01PM (#26080581)

The OP addresses your question, saying he is not advocating for removing laziness, but does have some specific suggestions.

> I'm not advocating for removing laziness in Haskell. In fact I'm not really advocating for much of anything in this series. I'm just complaining, because I like complaining.

> But if I was to advocate some changes:

  * Deprecate partial functions
  * Introduce a naming scheme for partial functions to be more obvious
  * Introduce a compiler warning to note partial function use (with a pragma to turn off specific usages)
  * Warn by default on partial pattern matches
  * Advocate strict data fields by default

[ Parent | on HN ]

Re:Haskell: The Bad Parts, part 2 (2020) by colonwqbang on Tuesday February 09, 2021 @02:48PM (#26081702)

Change all partial functions from returning a to returning Maybe a. Then we rename the fromJust function into the $%&!# operator (name intended to suggest the exclamation made by the programmer when function fails).

[ Parent | on HN ]

Re:Haskell: The Bad Parts, part 2 (2020) by _ezkx on Tuesday February 09, 2021 @07:29PM (#26084415)

If StrictData were simply made the new default (with exceptions for lists and some other things in the standard lib), I bet very little code would break. It certainly wouldn't change the flavor of the language. I think it's a good idea.

[ Parent | on HN ]