#10635: -fwarn-redundant-constraints should not be part of -Wall -------------------------------------+------------------------------------- Reporter: Lemming | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Compiler (Type | Version: 7.11 checker) | Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Incorrect | Unknown/Multiple warning at compile-time | Test Case: Blocked By: | Blocking: Related Tickets: #9939, #9973, | Differential Rev(s): #10100, #10183 | Wiki Page: | -------------------------------------+------------------------------------- Comment (by Lemming): I understand -Wall as the option that allows reasonably designed code to pass without warnings. There are good reasons to have redundant constraints as I sketched in the ticket description. It's crucial to be able to make code -Wall warning-free otherwise relevant warnings are easily overlooked in a flood of irrelevant warnings. According to my programming style I often add e.g. -fwarn-incomplete-uni-patterns -fwarn- tabs -fwarn-missing-import-lists. They match my style of programming but seem to interfere with other's style, thus they are not part of -Wall. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10635#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler