formal treatment of module dependencies

It seems to me that specifying and solving module dependencies is a ubiquitous problem in software development. All the languages that I know try to make the problem go away by using version numbers and maximizing backward compatibility. Does anyone know of references that formalize this problem for Haskell? Thanks, Dimitri -- 2E45 D376 A744 C671 5100 A261 210B 8461 0FB0 CA1F

Arguably, more sophisticated package-level module systems like Backpack are attempting to handle this problem, but we haven't tackled this particular incarnation directly. Excerpts from Dimitri DeFigueiredo's message of 2017-03-08 12:16:00 -0700:
It seems to me that specifying and solving module dependencies is a ubiquitous problem in software development. All the languages that I know try to make the problem go away by using version numbers and maximizing backward compatibility.
Does anyone know of references that formalize this problem for Haskell?
Thanks,
Dimitri
participants (2)
-
Dimitri DeFigueiredo
-
Edward Z. Yang