#10886: Remove the magic from `Any` -------------------------------------+------------------------------------- Reporter: goldfire | Owner: goldfire Type: task | Status: closed Priority: normal | Milestone: 8.2.1 Component: Compiler | Version: 7.10.2 Resolution: fixed | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Phab:D2049 Wiki Page: | -------------------------------------+------------------------------------- Comment (by simonpj): Replying to [comment:12 ezyang]:
The widespread use of GHC.Prim is primarily an accident induced by documentation: https://hackage.haskell.org/package/base-4.9.0.0/docs/GHC- Exts.html does not list all of the GHC.Prim functions; instead there's just a little "module GHC.Prim" deep inside. So if I'm looking up a function, the only Haddock page it is going to be on is GHC.Prim, and then of course I'm going to import GHC.Prim (if I am not paying close attention).
Indeed, our intent was that people should import `GHC.Exts` precisely to insulate them from the vaguaries of which module actually defines the thing. While that horse seems to have well and truly bolted, I wonder whether we could fix Haddock (or something) for the future, explain the intent, and encourage library authors to future-proof their code by updating their imports? Simon -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10886#comment:13 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler