[swift-build-dev] Namespacing SPM modules (was Re: [swift-dev] Right list?)

Max Howell max.howell at apple.com
Mon Feb 29 11:51:01 CST 2016

> I'm not sure this completely addresses my point... my argument was that while I understand the potential for collision when the major example is something related to "String", it still isn't clear to me that it is common enough to merit such a major feature. My point with examples like LLVM/libjpeg wasn't related to their style of package, but their uniqueness (which I see as a feature).

It’s not common, but it must be solved. I’m happy for us not to namespace if there is another solution that is just as good.

> Is the argument that this problem is more severe because we have no index?

Indeed, it’s more severe because there is no single index. 

> I think it would be good to see if we can get more data, too (e.g., more examples of collisions, or more evidence from other language communities).

We can try to get more data, but I’m not sure it’s necessary since even if the data says it happens only 1% of the time we cannot just leave users out in the cold in such situations.

There are several solutions, but namespacing seems most in the spirit of a decentralized packaging ecosystem that has emerged due to GitHub’s rise to prominence and its username/repo design.

However I’d be happy with any solution that works and is easy for the user to get on with things in the event go Module name collision.


More information about the swift-build-dev mailing list