Don't make pointer equality primops change breaking
Hi folks, I was reading the 9.4 migration guide and it seems there is a breaking change to pointer equality primops slated. Is it actually necessary for this to be a breaking change? Could the pointer equality primops be left where they are, with a warning to prefer using them from their new location instead, or even a {-# DEPRECATED ... #-}
? It would be nice not to break consumers unless absolutely necessary. If the removal of the pointer equality primops from that module can be postponed by a year or two this will give a nice smooth upgrade path to the new module, rather than forcing consumers to support GHC >= 9.4 exclusive-or GHC < 9.4.
cc @bgamari
See also #21276 (closed)