Norman's suggestion for warnings when building GHC. If we agree this we should
add it to guidance for developers:
1. Switch warnings off by default in build.mk.sample. Reason: too many are
generated.
2. Whenever a developer does non-trivial work on a module, ask them to
a) add {-# OPTIONS_GHC -Wall #-} to the top
b) modify the code (including stuff predating theirs) to eliminate
warnings
With a bit of luck, we'd get more and more modules with useful warnings; and
all warnings would be relevant.
Concerning 2(a) just which warnings do we want on? Norman's suggestion is: all
except name-shadowing. (ML heritage; but also useful in stateful monadic code.)
Does this seem plausible?
Simon
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
