This doesn't seem to work (easily) for me. I want -Wall applied to
all my source, so give it on the command line. Because the OPTIONS
options get prepended, the -Wall seems to win out. :(. I could add
-Wall at the top of all my source files, but that's unappealing. If
GHC provided a way
I wrote:
GHC's excellent warnings are very helpful. They would be somewhat
more so if it were possible to suppress a warning about a specific bit
of code
Then Simon Marlow [EMAIL PROTECTED] wrote:
(of course, the workaround is to put the offending code into a module of
its own, and
GHC's excellent warnings are very helpful. They would be somewhat
more so if it were possible to suppress a warning about a specific bit
of code. One possible syntax (to which I gave no commitment) would be
{-# WOFF non-exhaustive pattern matches #-}
offending code
{-# WON
If the switches take affect at the line granularity there would seem
to be a straightforward implementation that's orthogonal to most
everything else: store the excluded regions in separate data structure
and check that data structure before printing a message.
mike
GHC's excellent
GHC's excellent warnings are very helpful. They would be somewhat
more so if it were possible to suppress a warning about a specific bit
of code. One possible syntax (to which I gave no commitment) would be
{-# WOFF non-exhaustive pattern matches #-}
offending code
{-# WON non-exhaustive
