[RFC] "http-types" breakage / additions / rework

chrisdone: > I think the short answer is, “because the most popular compiler, GHC, only wants you to expose one version of a package at a time when doing a compile”, which makes it really hard to smoothly transition from one version to another, due to the mutual exclusion. I’m fairly confident that it’s this small tooling problem at the foundation of the stack that has caused huge ripple effects in the ecosystem that rests above it. This is no longer the case in GHC, GHC is capable of handling multiple versions of the same package. There is a POC for cabal private dependencies feature: Private Dependencies by alt-romes · Pull Request #9743 · haskell/cabal · GitHub which is, I think, conceptually what you would want. The limitation is that you cannot expose symbols of a private dependency, which may or may not be an issue in this particular instance.