Should exhaustiveness testing be on by default?
alexander.dunlap at gmail.com
Mon May 18 23:56:16 EDT 2009
On Mon, May 18, 2009 at 7:59 PM, Robert Greayer <robgreayer at gmail.com> wrote:
> On Mon, May 18, 2009 at 4:00 PM, Norman Ramsey <nr at eecs.harvard.edu> wrote:
>> P.S. The exhaustiveness checker does need improvement...
> Is it documented somewhere what deficiencies the exhaustiveness
> checker has (where it can report problems that don't exist or fails to
> report problems that do...), and which deficiencies can't be resolved?
One problem is that it reports erroneous errors when combined with
ViewPatterns, which certainly ought to be fixed if
-fwarn-incomplete-patterns and -fwarn-overlapping-patterns are
switched on by default. This isn't the bug others are referring to,
though; I don't know where you'd find that information.
More information about the Glasgow-haskell-users