[GHC] #10599: Template Haskell doesn't allow `newName "type"`

[GHC]

#10599: Template Haskell doesn't allow `newName "type"`
-------------------------------------+-------------------------------------
        Reporter:  meteficha         |                   Owner:  goldfire
            Type:  bug               |                  Status:  new
        Priority:  high              |               Milestone:  7.12.1
       Component:  Template Haskell  |                 Version:  7.10.2-rc2
      Resolution:                    |                Keywords:
Operating System:  Unknown/Multiple  |            Architecture:
 Type of failure:  None/Unknown      |  Unknown/Multiple
      Blocked By:                    |               Test Case:
 Related Tickets:                    |                Blocking:
                                     |  Differential Revisions:
-------------------------------------+-------------------------------------

Comment (by bgamari):

 It seems to me that we should be closing up the cases where `type` can be
 used as a name, not opening more of these holes. It would be quite
 confusing to the user if they end up with a situation where a they see an
 export named `type`, find that it can be imported without trouble if
 qualified, and then try to define another similarly named definition
 without of TH, only to find that they get a syntax error.

 I'm not entirely sure what we want to do about the parsing issue, but it
 seems that TH's current behavior is what we would want here, no?

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