PVP Compliance of .Internal modules

[atravers]

@hasufell

[…] GHC internals will be following PVP.

Likewise, some of the boot libraries will start following this pattern as well.

Can we at least try not to make the same mistake twice here:

• GHC extensions are not regular Haskell features,

• and “internal”/“low-level” libraries are not regular libraries.

…otherwise we are practically inviting everyone (again) to rely on their preferred set of such libraries as though they were regular ones (with a similar reaction to anyone contemplating major changes to them e.g. their deprecation).

Having 2^N combinations of GHC extensions is bad enough - do we really then want 2^M combinations of internal libraries pretending to be regular ones? Forget “explosion”, that would have to be a combinatorial “big bang!” I recall this thread:

[ANN] guardian-0.4.0.0 - A dependency boundary guardian for your Haskell monorepo to keep dependency sane and clean

It is our great pleasure to announce the first OSS release of guardian, a dependency boundary constraint checker for Haskell monorepo! If you have a trouble with Haskell monorepo with increasing complexity of the package dependencies, then guardian could help the situation! It is developed at DeepFlow, Inc. and has been used almost for two years. With guardian, you can divide the packages into several “domains”, and define the allowed dependency between those domains. Guadian will make sur…

…has anyone tried using this guardian system yet?