Re: [swift-corelibs-dev] libdispatch roadmap and api addition proposal

2015-12-10 Thread Joakim Hassila via swift-corelibs-dev
> On 8 dec. 2015, at 17:07, Pierre Habouzit wrote: > > My point is, adding API to dispatch is not something we do lightly. I’m not > keen on an interface that only works for base queues. Mac OS and iOS code > where dispatchy code is pervasive, more than 2 queue deep queues hierarchy is > very c

[swift-corelibs-dev] [xctest] Removing outliers from performance tests

2015-12-10 Thread Drew Crawford via swift-corelibs-dev
Hello folks, I’m one of the heavy users of XCTest.measureBlock as it exists in Xcode 7.2. To give some hard numbers, I have ~50 performance tests in an OSX framework project, occupying about 20m wall clock time total. This occurs on a per-commit basis. The current implementation of measureBl

Re: [swift-corelibs-dev] libdispatch roadmap and api addition proposal

2015-12-10 Thread Pierre Habouzit via swift-corelibs-dev
> On Dec 10, 2015, at 1:06 AM, Joakim Hassila via swift-corelibs-dev > wrote: > >> On 8 dec. 2015, at 17:07, Pierre Habouzit wrote: >> >> My point is, adding API to dispatch is not something we do lightly. I’m not >> keen on an interface that only works for base queues. Mac OS and iOS code >

Re: [swift-corelibs-dev] [xctest] Who tests the tests?

2015-12-10 Thread Brian Gesiak via swift-corelibs-dev
I've submitted https://github.com/apple/swift-corelibs-xctest/pull/14 as another attempt at this. Take a look at the pull request message for details. Turns out I'd overlooked another dependency: nearly all lit tests use FileCheck, which means to run the tests developers will need to specify that