[GHC] #15149: Identical distinct type family fields miscompiled

[GHC]

#15149: Identical distinct type family fields miscompiled
-------------------------------------+-------------------------------------
        Reporter:  NeilMitchell      |                Owner:  (none)
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:  8.6.1
       Component:  Compiler          |              Version:  8.4.2
      Resolution:                    |             Keywords:  ORF
Operating System:  Unknown/Multiple  |         Architecture:
 Type of failure:  GHC rejects       |  Unknown/Multiple
  valid program                      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by adamgundry):

 Yes, I can try to take a look at this.

 > My baseline thought is that `C { x = e1, y = e2 }` should have `x` and
 `y` as `OccNames` right up to the type checker. And that would be so in TH
 syntax to.

 I agree that this would be simpler (in the presence of
 `DisambiguateRecordFields`, `DuplicateRecordFields`, etc.). I'm concerned
 that it might impact TH users though, as they will have only an `OccName`
 where previously they had a `Name` (and they might not easily be able to
 reliably look up the `OccName` because of precisely this ticket).

 Should this go through ghc-proposals, or is there another process for
 discussing TH changes?

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