#8132: Warning for Typeable instances misplaced
-------------------------------------------------+-------------------------
Reporter: scottgw | Owner:
Type: bug | dreixel
Priority: normal | Status: new
Component: Compiler | Milestone:
Resolution: | Version: 7.7
Operating System: Unknown/Multiple | Keywords:
Type of failure: Incorrect warning at | Architecture:
compile-time | Unknown/Multiple
Test Case: | Difficulty:
Blocking: | Unknown
| Blocked By:
| Related Tickets:
-------------------------------------------------+-------------------------
Comment (by scottgw):
Well, assuming hand-coding {{{Typeable}}} instances is just as dangerous
as it was last release, then the first option is more appropriate. It will
allow more people to quickly move to 7.8 and find all the nasty bugs/great
features, which is what I guess everyone wants.
In this case, I would also keep {{{NewTypeable}}} in 7.10 as well, just
re-exporting {{{Typeable}}}. Then packages don't have a hard partition
between revisions and it gives maintainers a release to fix the 'typo'.
Otherwise it makes the advice in 7.8 strange: the old {{{Data.Typeable}}}
is being deprecated, please use the (deprecated) {{{Data.NewTypeable}}}.
The churn will be constant in either case, but this keeps the user-facing
breakages down.
I would be happy to help make the changes as well, if someone were to
point me to the relevant places.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8132#comment:8>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
ghc-tickets mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/ghc-tickets
