Thanks Adam,
I'm not too familiar with the GHC-side requirements here, but I wonder
if we can approach this issue from a different direction: is there
something we can do to help boot libraries avoid breaking changes?
Tom
Breaking changes caused by new exports could be mitigated with a library package or a GHC plugin with such auto refactoring functionality :
* Uniquely qualify (i.e., leave no different modules similarly qualified in the same module) each imported module and each imported symbol.
This refactoring should be possible in code which already compiles.
It would not require syntax / grammar changes.
Something similar to smuggler2 package.