<div dir="ltr">I have never once felt a need to distribute a library with an icon<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 22, 2017 at 10:43 AM, Karl Wagner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
> On 21. Sep 2017, at 18:51, Karl Wagner via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> Hi everybody!<br>
><br>
> I’m really happy that Swift 4 is out, and it’s great that there’s already so much active discussion about Swift 5 (concurrency, etc). I find I’m running in to language roadblocks less and less, and the improvements to the generics system have really improved a lot of my code. It’s really enjoyable to program in Swift, so thanks to everybody who made it possible.<br>
><br>
> When I think about what’s missing from Swift, I think of modules. We all like to write modular code, and aside from the entire discussion about submodules, the way that you glue separate modules together in to an application is supposed to be via the package manager. For Swift 5, I would personally really like it if we could flesh out the package manager a bit more so that it can really be the basis of a thriving Swift developer community in production environments.<br>
><br>
> The thing that hits me the most with SwiftPM currently is that it doesn’t support resources, and it has very limited support for cross-platform modules (the type of thing you’re likely to have as a Model or Model Controller layer). Without support for bundled application resources, there’s no way for the package manager to support GUI apps or frameworks and unit-tests can’t reliably point to bundled test resources.<br>
><br>
> I have some ideas about ways we could improve the situation, but first I thought I’d send this out for some community feedback. Do you think SwiftPM is as important as I do for v5? Which improvements would give you the most benefit?<br>
><br>
> - Karl<br>
><br>
> ______________________________<wbr>_________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br>
</div></div>Title is rubbish (copy/paste error). Should be “SwiftPM in Swift5”.<br>
<br>
But seriously, one of the themes from the discussions in the past release was that “there’s no good library for X” or “when will people use Swift for Y?”. I believe the package manager is a big hurdle to getting more, great libraries in wider use. CocoaPods is far from sufficient. Thinking about this hypothetical future Xcode integration; how is that even supposed to happen when the package manager doesn’t support Apps with bundled resources (like icons)?<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br></div>