#3665: Add whole-package deprecation warnings
---------------------------------+------------------------------------------
Reporter: duncan | Owner:
Type: feature request | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 6.12.1 RC1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Os: Unknown/Multiple
Architecture: Unknown/Multiple |
---------------------------------+------------------------------------------
Changes (by simonpj):
* difficulty: => Unknown
Comment:
Is the module itself the right place for such a message? After all, if
you deprecate a package you probably deprecate all the exposed modules in
the package, so it's a bit tedious to have to do that module by module.
Moreover, the identical code might appear in an updated version of the
package, so it's not really that ''code'' that's deprecated; it's the
context in which it appears.
Isn't the `.cabal` file the right place to deprecate a package? After
all, that's where all its metadata is given. And Cabal itself might like
to know about deprecations during its ruminations, not just GHC.
So I'm unconvinced.
Simon
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3665#comment:1>
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
