SE-0339: Module Aliasing for Disambiguation

[SDGGiesbrecht (Jeremy David Giesbrecht)]

@elsh

If there are multiple aliases specified for a module, it will throw an error during dependency resolution and fail to build. If a module has been aliased lower down, there shouldn't be a need to alias it again at the top level.

Let me give an example of what I mean. Imagine the following desired package graph, where every module is different:

MyPackage
  Gaming
    Sound (moduleAliases: [Utils: SoundUtils])
      Utils
    Utils
  Music
    Sound (moduleAliases: [Utils: SoundUtils])
      Utils
    Utils

With a standard dependency declaration, “MyPackage” would have two clashing “SoundUtils” and at least two clashing “Utils” modules. What should it specify in moduleAliases for one or both of its dependencies in order to resolve the problem?