Lisp and Haskell (2017)

Re:Lisp and Haskell (2017) by YouAreGreat on Sunday July 15, 2018 @06:13AM (#17534600)

Here's an observation from Benjamin Pierce, static typing guru:

> Complex definitions tend to be wrong when first written down. In fact, not only wrong but nonsensical. Most programming errors are not subtle!

Static type systems will tend to find those bugs. They're not subtle!

Running the code—just once—will also tend to find those bugs. They're not subtle!

[ Parent | on HN ]

Re:Lisp and Haskell (2017) by crabmusket on Monday July 16, 2018 @10:46AM (#17541669)

Syntax can also help here. Complex or verbose syntax can make bugs that aren't actually subtle much harder to spot. A readable syntax, API, or even an EDSL can make errors more obvious by making incorrect code _look_ incorrect.

And of course naming things is a huge part of this, not just the raw syntax.

[ Parent | on HN ]