<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif">Have you tried typealias? typealias NewTypeName = Module.TypeInsideModuleName</div><div class="gmail_default" style="font-family:georgia,serif"><br></div><div class="gmail_default" style="font-family:georgia,serif">zhaoxin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 2, 2016 at 9:41 AM, Jason Lee via swift-users <span dir="ltr"><<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
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.<br>
<br>
An example:<br>
Package 'A' has a module named 'Base'<br>
My package also has a module named 'Base'<br>
<br>
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:<br>
<br>
import Foundation<br>
import Base<br>
import MyAppBase<br>
<br>
Any thoughts on this? Thx.<br>
<br>
- jason<br>
<br>
Sent from my iPhone<br>
_______________________________________________<br>
swift-users mailing list<br>
<a href="mailto:swift-users@swift.org">swift-users@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-users</a><br>
</blockquote></div><br></div>