<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Not in practice (with respect to package manifests). In fact, it seems that, given there are separate commands (swift build and swift test), separate directories (Sources and Tests), and separate products, that there's a hole to be filled here by separate handling for test suites in package manifests.</div></div></blockquote><div><br></div><div>FWIW, overriding conventions will potentially allow you control the layout of the package (when we have that feature).</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div> </div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div></div><div>This is all not to discount the features you've brought up as well, but I'm having trouble seeing why a distinction here is such a problem.</div></div></blockquote><div><br></div><div>Could you elaborate on what kind of distinction are you proposing? Is it separating targets and testTargets?</div><div><br></div><div>-- <br></div></div><div class="gmail_signature" data-smartmail="gmail_signature">Ankit<br><br></div>
</div></div>