Skip to content

Export lists: give the same priority to a NoParent GRE and one that has the right parent

sheaf requested to merge sheaf/ghc:T25892 into master

Ticket: #25892 (closed)

This MR ensures that, when we are renaming children in an export list item such as

module M ( P(A,B,C) )

we consider children with NoParent to have the same priority as children which have the correct parent (P in this case). This is because we should not prioritise a data constructor (with the right parent) over a pattern synonym we are bundling (which, before bundling, has no parent).

Merge request reports