[GHC] #12457: Deriving should be (more closely) integrated with other metaprogramming methods

[GHC]

#12457: Deriving should be (more closely) integrated with other metaprogramming
methods
-------------------------------------+-------------------------------------
        Reporter:  mpickering        |                Owner:
            Type:  feature request   |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Compiler          |              Version:  8.0.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by mpickering):

 Richard comments:

 >> * Template Haskell: Not portable. Staging issues make it hard to use
 >> as a drop-in replacement for the `deriving` keyword
 >
 >I do not understand "not portable" here. Do you mean that some
 architectures don't support TH?
 >
 >What staging issues?
 >
 >I'm imagining here having `deriving Blah` be surface syntax that desugars
 into some TH splice. You keep the nice user-facing syntax, but make the
 deriving mechanism itself specified in TH code.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/12457#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler