[swift-evolution] [Draft] Test-Only Package Dependencies and Targets
devteam.codafi at gmail.com
Mon Jan 30 13:55:05 CST 2017
> On Jan 30, 2017, at 2:38 PM, Ankit Agarwal <ankit at ankit.im> wrote:
> 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.
> FWIW, overriding conventions will potentially allow you control the layout of the package (when we have that feature).
In that case, as long as there are plans for this kind of feature, I can hold off on submitting this proposal until it materializes.
> 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.
> Could you elaborate on what kind of distinction are you proposing? Is it separating targets and testTargets?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution