Regardless of if -Wcompat is on by default or not, the timeline for changes
wouldn't change. The only thing that would change is that we'd be asking
library authors to use
-Wall -Wno-compat
which they can't do on old versions of GHC, so it'd become a bigger burden
for the lion's share of library maintainers; they'd have to explicitly
guard the -Wno-compat flag on the GHC version in their cabal file.
At least those who _want_ -Wcompat are explicitly looking forward and it
seems right to put the burden on that smaller subset than change the game
for every library maintainer.
Mind you if a -Wcompat user isn't looking to support old versions, they
also have no burden.
But, again, switching the default wouldn't gain you any time on any
outstanding proposal.
-Edward
On Mon, Nov 30, 2015 at 3:10 AM, Jeremy
The current design is that -Wcompat will be off by default and includes warnings that are not in -Wall and that we'll be introducing warnings into -Wall when they become actionable under a 3 release policy rather than
Edward Kmett-2 wrote the
more eager approach you are advocating here.
Yes, I understand that that is the current design, and I'm asking whether this could be adjusted. Do we lose anything by the proposed change to the policy, other than authors who want 3-release -Wall-clean code adding an extra flag? (Or maybe I just didn't understand you - are you saying that introducing new warnings are not a bottleneck for any changes?)
-- View this message in context: http://haskell.1045720.n5.nabble.com/3-release-policy-and-Wno-compat-tp58232... Sent from the Haskell - Libraries mailing list archive at Nabble.com. _______________________________________________ Libraries mailing list Libraries@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries