<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Without a better C/C++ integration story, Swift is still born in my world.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 28, 2017, at 8:04 AM, Goffredo Marocchi via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Very well said, I kind of think that at this point in time you do much more for the language by investing into SPM properly than Actors/Coroutines if you had to choose.<br class=""><br class=""><div class="">Sent from my iPhone</div><div class=""><br class="">On 28 Oct 2017, at 14:26, Karl Wagner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 23. Oct 2017, at 19:41, Jean-Christophe Pastant via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class="">Hi,<br class=""><br class=""></div>Is there any news about features that are willling to be integrated into SPM 5?</div><div class="">Those I see the most relevant:<br class=""></div>- iOS support<br class=""></div>- Some kind of configuration/settings support (debug, release, ...)<br class=""><div class=""><div class=""><br class=""></div><div class="">I'd like to hear about it from <span class="gmail-_Tgc">maintainers, especially if there's a priority order we should follow.<br class=""></span></div><div class=""><br class="">Regards,<br class=""><br class=""><br clear="all" class="">
</div></div></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""><div class="">Yup. My opinions here: <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170918/039885.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170918/039885.html</a>. Basically, I think we need support for 1) resources (or ‘assets’) and 2) cross-platform modules.</div><div class=""><br class=""></div><div class="">I think that a better package-manager would really accelerate the Swift ecosystem. We’ve had lots of people complaining about the lack of quality libraries (e.g. for maths and stats) during the Swift 3/4 phases. Personally, I still think it’s too much effort to integrate 3rd-party library projects in to my existing projects and to contribute to them, which is why I usually don’t.</div><div class=""><br class=""></div><div class="">As for Xcode integration: Obviously only Apple can comment on the Xcode roadmap - but I will point out that, like the rest of Swift and LLVM, the package manager is open-source and designed with a library architecture. That means that any IDE could integrate support for SwiftPM, not just Xcode. As users, we can say what <i class="">we’d like</i> Apple to do with Xcode, but it’s all academic - since SwiftPM doesn’t support bundled assets, it <i class="">can’t</i> support graphical applications. Bundled assets aren’t just an issue for GUI applications, though - localisation tables, prepared databases and test resources are useful for any kind of package.</div><div class=""><br class=""></div><div class="">So, for me the issue with assets is that some platforms have unique compiled formats (e.g. Apple’s asset catalogues) which support asset variants for localisations and display resolution. Obviously I want my output App to support all of these features. In fact, most modern platforms have support for some kind of asset variants — Apple calls it a TraitCollection, Android calls it a Context — so do we want to support this concept natively somehow in SwiftPM?</div><div class=""><br class=""></div><div class="">I mean, let’s say I have this awesome cross-platform Swift application/library, and I’ve listed some files in my Package.swift and I can find them again at runtime on any platform - all cool. Now, I want to localise my package - what do I do? I’m going to have to create some middleware to translate platform-specific concepts in to a baseline which I can look-up based on some mangling I’m going to create for the file names. Localisation is a problem on servers, too (particularly for error messages), so some idea of asset variants could be something universal-enough to include in the package manager.</div><div class=""><br class=""></div><div class="">- Karl</div></div></div></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>