#1911: -w doesn't turn off nullModuleExport
---------------------------+------------------------------------------------
Reporter: AndreaRossato | Owner: AndreaRossato
Type: bug | Status: assigned
Priority: normal | Milestone: 6.10 branch
Component: Compiler | Version: 6.8.1
Severity: minor | Resolution:
Keywords: | Difficulty: Easy (1 hr)
Testcase: | Architecture: Multiple
Os: Multiple |
---------------------------+------------------------------------------------
Comment (by simonmar):
Replying to [comment:11 AndreaRossato]:
> So I'm attaching a new patch, which correctly deals with the second
issue.
Looks fine, modulo your suggestions below.
> I also want to rephrase my other question about the possibility of
adding more specific warnings instead of a general wanr-misc: the warning
about exporting T(..) when T is a synonym is treated similarly to the
warning for importing T(..) when T is exported abstractly. For this second
case there is a flag: -fwarn-dodgy-imports. Shouldn't we add a
corresponding -fwarn-dodgy-exports?
Yes, that sounds like the right thing.
Rule of thumb: if `-fwarn-misc` would only cover one or two warnings, it
would be better to give them separate flags. If we can find a handful of
things to put in `-fwarn-misc`, then it becomes worthwhile.
> This second was seems more consistent to me (obviously the patch will
include all the needed documentation update too).
>
> Sorry for the noise: I'm learning.
No problem, thanks for getting involved!
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1911#comment:12>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
