Language, library, and compiler stability (moved from GHC 9.6 Migration guide)

Sure, but let’s not pretend we’re anywhere near what rustc does:

  1. there is a very strict 3-steps procedure wrt breaking changes that can take years
    • introduce a lint
    • make the lint deny by default
    • make it a hard error
  2. breaking changes are widely discussed in the community before they’re introduced via the above procedure (also may take years)
  3. there’s a strong motivation by the compiler team to keep backwards compatibility

I don’t think we have any of those points implemented. That was my point, not whether the current breakage in 9.6 would require a deprecation procedure or not.

This difference is very stark and should serve as a reference point when discussing diverging goals in our community.

5 Likes