<div dir="ltr">CORRECTION: -fwarn-trustworthy-safe was not in -Wall in GHC 7.8, but -fwarn-trustworthy-safe did not exist in GHC 7.8.<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 5, 2015 at 10:54 AM, Omari Norman <span dir="ltr"><<a href="mailto:omari@smileystation.com" target="_blank">omari@smileystation.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div>I noticed some significant changes to the flags included with -Wall in GHC 7.10. Many flags that were previously included in -Wall are now not included. These include:<br><br></div>-fwarn-type-defaults<br></div>-fwarn-name-shadowing<br></div>-fwarn-missing-signatures<br></div>-fwarn-hi-shadowing<br></div>-fwarn-orphans<br></div>-fwarn-unused-do-bind<br></div>-fwarn-trustworthy-safe<br><br></div>I can't find any mention in the release notes of this change in behavior.<br><br></div><div>I was wondering what the rationale is for these changes? Any link to relevant discussion would be appreciated if it exists.<br><br>Also, what opinion do people have? I previously kept my code -Wall clean, but sometimes that would be a pain. For instance I would munge local names so they wouldn't trigger -fwarn-name-shadowing, and I would add signatures to integers so they wouldn't trigger -fwarn-type-defaults. In fact, I only noticed this change in behavior in 7.10 because I was considering dumping -Wall, and when I looked at the 7.10 manual I saw that it does not enable -fwarn-name-shadowing. (I still use 7.8 but Google pulled the 7.10 manual.) Does this change indicate that people were finding -Wall too onerous and, thus, not using it?<br><br>I do remember reading complaints about -fwarn-unused-do-bind being added to -Wall, but I previously felt dirty about name shadowing though I wondered if munging names to avoid shadowing was actually worse.<br></div></div>
</blockquote></div><br></div></div></div>