Should exhaustiveness testing be on by default?

[Lennart Augustsson]

The exhaustiveness checker in ghc is not good.  It reports
non-exhaustive matching a bit too often and also the error messages
are often not in terms of the original source but some desugared
version.

If those things were improved I think it should be always on.

On Mon, May 18, 2009 at 12:53 AM, Don Stewart <dons at galois.com> wrote:
>
> I'm not sure I'd want -Wall on by default (though being -Wall clean is
> very good). But exhaustive pattern checking might well help out a lot of
> people coming from untyped backgrounds.
>
>    http://ocaml.janestreet.com/?q=node/64
>
> Ron's also wondering why exhaustive pattern checking isn't on ?
>
> Anyone know why it isn't the default?
>
> -- Don
> _______________________________________________
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
>