
I don't have any personal experience with the new warning, but it does sound to me like there are two separate warnings (redundant vs unused constraints) combined under a single flag. So I would support separating them! On Sat, Jun 11, 2016, at 09:38, Carter Schonwald wrote:
Either way, do we have a strong agreement that for ghc 8.2 that this warning should be split up and the noiser part should be moved out of the default wall set?
On Monday, June 6, 2016, Carter Schonwald
wrote: To better elaborate : I definitely want this for the next major version i.e. 8.2.* , but I'm also wondering if perhaps the "overly constrained type" warning should be flat out removed from Wall even in ghc 8.0.2,
On Monday, June 6, 2016, Carter Schonwald
javascript:_e(%7B%7D,'cvml','carter.schonwald@gmail.com');> wrote: It's a tall ask, but why not? On Jun 6, 2016 12:16 PM, "Eric Seidel"
wrote: On Mon, Jun 6, 2016, at 07:37, Carter Schonwald wrote:
I don't suppose there's any hope of having this resolved prior to GHC 8.2 because it is a real usability regression? Because I think we can all agree that the proposed change would not break any 8.0 series code, and positively impact everyone.
Do you mean prior to 8.0.2? _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users