[swift-users] Package module name collisions
jasonlee9 at gmail.com
Wed Feb 3 17:20:21 CST 2016
I decided to go the longer name route. This has solved my issue - for now. I will keep my eye open for the proposal, thanks!
> On Feb 3, 2016, at 3:16 PM, Max Howell <max.howell at apple.com> wrote:
> Hi Jason,
> module-name collision is something that keeps me up at night. I intend to solve it as properly as possible.
> This will involve a proper proposal for swift proper down the line, probably involving namespacing in some form.
> For now, you can either cross your fingers or fork the project that has the collision and change the module name.
>> On Feb 1, 2016, at 5:41 PM, Jason Lee via swift-users <swift-users at swift.org> wrote:
>> Today I introduced a dependency on another project's package with brought over a module name that conflicted with one he modules in my project.
>> Currently my project has multiple modules (and executables) in the package and everything is working well for me. However, when I got this conflict today, I was thinking this will be a problem going forward. I'm sure it's been solved already by the package manager team, but I haven't figured out how to do this from the docs yet.
>> An example:
>> Package 'A' has a module named 'Base'
>> My package also has a module named 'Base'
>> When I build, I get a circular ref error now. One way I was thinking I cld fix this on my end is to prefix all my module names with my package name (seems redundant, of course). Something like 'Base' becomes 'MyAppBase'. And my imports could look like so:
>> import Foundation
>> import Base
>> import MyAppBase
>> Any thoughts on this? Thx.
>> - jason
>> Sent from my iPhone
>> swift-users mailing list
>> swift-users at swift.org
More information about the swift-users