<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">We discussed variadic overloads during the manifest redesign proposal but ultimately <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0158-package-manager-manifest-api-redesign.md#alternatives-considered" class="">rejected</a> it. We could add an overload for a singular source file (instead of variadic) but I think its simpler to just have one option, and it is also easier when you want to extend your source list form one to two.<div class=""><br class=""></div><div class="">I think parsing is not a concern because tools are expected to ask for JSON representation and not directly parse the swift file.<div class=""><br class=""><div class=""><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On 29-Mar-2017, at 11:18 PM, David Sweeris <<a href="mailto:davesweeris@mac.com" class="">davesweeris@mac.com</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=""><div class=""><span class=""></span></div><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div class=""><br class=""></div><div class="">On Mar 29, 2017, at 10:19, Ankit Aggarwal via swift-build-dev <<a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div dir="ltr" class="">The <a href="https://github.com/aciidb0mb3r/swift-evolution/blob/custom-targets-layout/proposals/NNNN-package-manager-custom-targets-layout.md" class="">proposal</a> is updated with this change.</div></blockquote><br class=""><div class="">What do we think about adding convenience inits that take a single parameter in place of the []s, for when we're only passing one value?</div><div class=""><br class=""></div><div class="">The down side is that it makes it more complicated for 3rd party tools to parse. Dunno if that's a concern.</div><div class=""><br class=""></div><div class="">- Dave Sweeris</div></div></div></div></blockquote></div><br class=""></div></div></div></div></div></body></html>