Fix situation with Data.Enum and Data.Bounded in base

@Bodigrim writes in !11347 (closed)

The proposal meant to introduce Data.Bounded for class Bounded and Data.Enum for class Enum. Yet in base-4.20 I observe Data.Enum with both type classes, but no Data.Bounded at all. There is neither changelog nor @since pragma. Even more confusingly, this MR is still unmerged. What's happening?

changed milestone to %9.12.1

assigned to @bgamari

added needs triage label

added Tbug core libraries labels and removed needs triage label

@bgamari replies in !11347 (comment 586548)

Sigh, yes, this looks to be a bit of a mess. The introduction of Data.Enum very likely inadvertently happened in the ghc-internal refactoring (where it was originally introduced to ensure that the exports of GHC.Enum were available from outside the GHC. module namespace) while this MR slipped through the cracks.

I suppose this raises the question of how we should mitigate the effects of this mess. Given that this has sadly made it into a release I suspect that the right approach is to deprecate the export of Bounded from Data.Enum and continue with the introduction of Data.Bounded (e.g. in %9.12.1). How does this sound to you?

mentioned in merge request !11347 (closed)

Given that this has sadly made it into a release I suspect that the right approach is to deprecate the export of Bounded from Data.Enum and continue with the introduction of Data.Bounded (e.g. in %9.12.1). How does this sound to you?

+1 from me, not sure what other CLC members think about it.

I have implemented this in !11347 (closed).

@Bodigrim, would you like me to open a CLC proposal to discuss this or should we just move ahead?

changed milestone to %9.14.1

changed milestone to %9.12.1

Fixed by !11347 (closed)

closed