-fwarn-redundant-constraints should not be part of -Wall
|Reported by:||Lemming||Owned by:|
|Component:||Compiler (Type checker)||Version:||7.11|
|Keywords:||Cc:||mboes, edgar.zhavoronkov, RyanGlScott|
|Type of failure:||Incorrect warning at compile-time||Test Case:|
|Related Tickets:||#9939, #9973, #10100, #10183, #11370||Differential Rev(s):||Phab:D2498|
When I compile existing code with GHC-7.11.20150707 I get lot of "redundant constraints" warnings. Generally I think that this warning can be very useful for minimizing constraints, nonetheless there are good reasons not choose minimal constraints for a type signature. E.g. if I have to implement Data.Map.singleton I do not need the Ord k constraint for the key type. However, I might add it anyway in order to be able to change the implementation in future such that it uses Ord k dictionary.
Thus I suggest to exclude -fwarn-redundant-constraints from -Wall.
Change History (37)
comment:9 in reply to: ↑ 8 Changed 11 months ago by Lemming
comment:33 Changed 5 months ago by simonpj
- Milestone set to 8.0.2
- Priority changed from normal to highest