[GHC] #14307: NamedFieldPuns should allow "ambiguous" field names

[GHC]

#14307: NamedFieldPuns should allow "ambiguous" field names
-------------------------------------+-------------------------------------
        Reporter:  mgsloan           |                Owner:  (none)
            Type:  feature request   |               Status:  new
        Priority:  low               |            Milestone:
       Component:  Compiler          |              Version:  8.2.1
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
                                     |  rename/should_fail/T14307
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by Simon Peyton Jones <simonpj@…>):

 In [changeset:"7720c293e7f5ca5089e3d154aad99e8060d6ac63/ghc"
 7720c293/ghc]:
 {{{
 #!CommitTicketReference repository="ghc"
 revision="7720c293e7f5ca5089e3d154aad99e8060d6ac63"
 Tidy up some convoluted "child/parent" code

 In investigating something else (Trac #14307) I encountered the
 wonders of TcRnExports.lookupChildrenExport, and the data
 type ChildLookupResult.

 I managed to remove the NameErr constructor from ChildLookupResult,
 and simplify the code significantly at the same time.

 This is just refactoring; no change in behaviour.
 }}}

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