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

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] [xctest] Removing outliers from performance tests

> Unfortunately our corelibs implementation of XCTest isn’t ready yet for > performance testing. That's why I'm here; I'm taking the temperature on implementing it. I'm at the pain level where I need a solution in the next several months, even if the solution is to code it up myself. My tests

[swift-corelibs-dev] #if __CORELIBS_FOUNDATION__

Hi folks, I notice that swift-corelibs-foundation is (apparently) deliberately incompatible with Darwin Foundation (https://github.com/apple/swift-corelibs-foundation/blame/master/Foundation/NSFileManager.swift#L324

[swift-corelibs-dev] bridging (SR-138)

I've noticed that e.g. String is not bridged to NSString. The expected workaround seems to be calling .bridge() everywhere. 1. Is there a plan for bridging e.g. String with NSString? 2. Would it be appropriate to PR in the meantime e.g. extension String { public func cStringUsingEncod

[swift-corelibs-dev] relationship of CF

I had a question about something I saw in the docs: > A significant portion of the implementation of Foundation on Apple platforms > is provided by another framework called CoreFoundation (a.k.a. CF). CF is > written primarily in C and is very portable. Therefore we have chosen to use > it for

Re: [swift-corelibs-dev] #if __CORELIBS_FOUNDATION__

> On Jan 4, 2016, at 3:09 PM, Tony Parker wrote: > > In this particular case, how would you use the #if? Any should be source > compatible with AnyObject, since Any is a superset of AnyObject, right? Well I don't know what you mean by "compatible" but the thing about strongly typed languages