#5275: Data.Typeable not backwards compatible
---------------------------------+------------------------------------------
Reporter: augustss | Owner: simonmar
Type: bug | Status: new
Priority: high | Milestone: 7.2.1
Component: libraries/base | Version: 7.1
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by simonmar):
Replying to [comment:4 batterseapower]:
> I don't think Lennart wanted a way to deconstruct a TyCon. He just
wanted equality on TyCon strings to be a) backward compatible and b) not
reveal implementation details about where "built-in" types like Int were
actually declared. Do you plan to do something separate to address that
point?
The specific problem is that `tyConString` returns a string that is not
portable and reveals implementation details. Making `tyConString` return
just the name of the !TyCon and not its implementation module would fix
that. We also need a way to uniquely identify !TyCons, and the hash
provides that - the hash would be the Md5 of "package-1.0:Module.TyCon",
but computed at compile-time because it's easier. The other fields are
just for information (we'll probably provide GHC-specific ways to get at
them).
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5275#comment:5>
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
