If anything, I'd flip those two... On the backend, things are anything but pure but it helps us reason about the program on the front end. Laziness also isn't nearly as prevalent on the backend as it is on the front end. Even though we can reason about things using purity and laziness on the front, the compiler often times makes an identical situation that runs a lot faster using strictness and mutation on the back. /jve On Thu, Dec 10, 2009 at 11:09 AM, John D. Earle <JohnDEarle@cox.net> wrote:

Laziness is on the logic front end and purity is on the execution back end.

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe