#8337: make it possible for the user to force orphanness via a module-level annotation -------------------------------+------------------------------------------- Reporter: errge | Owner: Type: bug | Status: patch Priority: normal | Milestone: 7.8.1 Component: Compiler | Version: 7.6.3 Resolution: | Keywords: Operating System: | Architecture: Unknown/Multiple Unknown/Multiple | Difficulty: Easy (less than 1 hour) Type of failure: | Blocked By: None/Unknown | Related Tickets: Test Case: | Blocking: 7867 | -------------------------------+------------------------------------------- Comment (by simonpj): I'm not sure about this errge. Can't you detect orphan-ness directly? For rules, say, a module is an orphan if it has a RULE for a function that is not defined in this module. So for annotations, could you not say that a module is an orphan if it has annotations for entities (types, classes, functions) that are not defined in this module? Mind you, the [http://www.haskell.org/ghc/docs/latest/html/users_guide /extending-ghc.html#annotation-pragmas manual section on annotations] seems to only allow annotations on things defined in this module. So then ''no'' module is an orphan. I'm pretty confused. More information, and user documentation for this feature, would be helpful. Simon -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/8337#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler