Oleg Grenrus

FWIW, https://gitlab.haskell.org/haskell/prime/-/wikis/libraries/3-release-policy starts with > Changes to the basic libraries, especially the Prelude, can be disruptive So the three release policy can be (and IMO that was the initial intention)...

> You can always express GHC SC principles as conditional on CLC actions, e. g., "GR1. If CLC did not break working code, GHC SC also aspires not to break...

> urated by CLC is not fundamentally different in its impact on users from bytestring or containers. Indeed, and Simon is not asking `bytestring` or `containers` maintainers to write the...

It could be documented that `Eq` instance witnesses equivalence ``(==) `on` render``, thus for most combinators in the library substitutivity indeed doesn't hold. *pr welcome*

Everything looks fine. I'm waiting for GHC-9.10 release; as this is still a breaking change, I'd like to make a 9.10 compatibility work first, and only then make a major...

One option, which is not breaking, and may fix part of #27 is to use `forall a. Ord a => Ord (f a)` implied by `Ord1 f` in the implementation,...

Well... > Deprecation. Deprecated entities (via a DEPRECATED pragma) SHOULD be counted as removed for the purposes of upgrading the API, because packages that use -Werror will be broken by...

@andreasabel yes, but also other versions in `attoparsec`.

I'm not thrilled by treating one special case of a bigger problem. As I just commented on the issue it's IMO problem in the grammar specification. `try` is no good.

See previous proposal https://github.com/haskell/core-libraries-committee/issues/171, seems CLC wanted first deprecation, and only then removal.