<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=""><blockquote type="cite" class="">but let's be careful not to make the perfect the enemy of the good here.</blockquote><div class=""><br class=""></div><div class="">This ship has sailed: it is the present policy to make perfect the enemy of the good, <a href="https://github.com/apple/swift-package-manager/pull/107#issuecomment-168847823" class="">or, as others word it</a>:</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""> it doesn't usually make sense to add features that we consider actively/potentially harmful, even if that solves some current short term pain.</blockquote></div><div class=""><br class=""></div><div class="">I don't necessarily agree with the policy but I do think it should be consistently applied. If we know we're going to refactor the XCTest interface later we shouldn't implement it the wrong way now, or else we should implement everything the wrong way now if it solves a present short-term pain, but there is nothing unique about the testing feature that does not equally apply to other situations.</div></body></html>