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

GHC ghc-devs at haskell.org
Tue Oct 3 15:42:25 UTC 2017


#14307: NamedFieldPuns should allow "ambiguous" field names
-------------------------------------+-------------------------------------
        Reporter:  mgsloan           |                Owner:  (none)
            Type:  feature request   |               Status:  closed
        Priority:  low               |            Milestone:
       Component:  Compiler          |              Version:  8.2.1
      Resolution:  fixed             |             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 mgsloan):

 Great, thanks for the quick fix Simon!

 > Yes, but you need -XDisambiguateRecordFields for that (​user manual
 entry). Haskell 2010 specifies that the code is should be rejected. So I
 think GHC is behaving right here.

 Interesting, I didn't know about that one, cool!  Glad there's a way
 around that one.  Perhaps the error message could mention the extension
 since it's a rarer one?

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


More information about the ghc-tickets mailing list