[swift-build-dev] Revisiting package conflicts

Erica Sadun erica at ericasadun.com
Thu Mar 31 17:20:27 CDT 2016

*headbang* *headbang* *headbang*

Possible situations:

* One package knows there's name conflicts, uses full dependency reverse namespacing
* Dependent package does not know there's name conflicts, but it has a dependency listed, so it uses only the nearest/most visible declaration.

Is there a way to resolve using some sort of rule system so that this somehow works? Can I assume that each module is compiled from the bottom to the top of the dependency graph so that the only conflicts ever seen would be higher in the graph where they know a priori that there's a more complicated import?

-- E

> On Mar 31, 2016, at 12:37 PM, Ankit Agarwal <ankit at ankit.im> wrote:
> I think if swiftpm renames `SwiftString` to `com.github.erica.SwiftString`, any other dependency having either `SwiftString` as dependency will not be able to use `import SwiftString` and thus fail to build.
> On Thu, Mar 31, 2016 at 11:54 PM, Erica Sadun <erica at ericasadun.com <mailto:erica at ericasadun.com>> wrote:
> I'm trying to clean up a few things while my kids are on Spring Break and decided to rewrite my package
> conflict proposal, which follows.
> This updated version does not require any language change (although one could be adopted later), does not
> require any package change, and only affects the target directories and module names.
> I'd appreciate any feedback you could give.
> Thanks, -- Erica

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20160331/30724084/attachment.html>

More information about the swift-build-dev mailing list