#7867: Allow template-haskell to communicate with itself between compilation units through the interface file --------------------------+------------------------------------------------ Reporter: errge | Owner: Type: | Status: patch feature request | Milestone: 7.8.1 Priority: | Version: 7.6.3 normal | Keywords: Component: | Architecture: Unknown/Multiple Template Haskell | Difficulty: Easy (less than 1 hour) Resolution: | Blocked By: 3725, 8337, 8340, 8397, 8398 Operating System: | Related Tickets: Unknown/Multiple | Type of failure: | None/Unknown | Test Case: | Blocking: | --------------------------+------------------------------------------------ Comment (by simonpj): errge, I've been talking to Austin It's very late in the day for 7.8, and we are still discussing the ''design''. So I don't think we can put this in 7.8, otherwise we'll mess it up and/or commit to a design that we subsequently regret. Can you start a GHC Trac wiki page to describe clearly * The use-case you have in mind. Along the lines you have given recently in #8337, but can you give a small concrete example? I still don't get it; for example, is `tcp_connect_timeout` exported, and if not what good is it? * The programmer's-eye view of the design (eg the TH API changes). For example, I'm very dubious about `qReifyModules` because the notion of the "list of modules that are known to the compiler" is such an ill-defined one. Imagine if you were writing a new Haskell compiler: how would you implement that API? What is its actual semantics? * A sketch of the implementation changes needed (and links to tickets) That would help more people participate in the conversation. At the moment you are implementing solutions to problems that we don't understand! Thanks Simon -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/7867#comment:12 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler