t;
>>> Chris
>>>
>>>
>>>
>>>
>>> From: Luke Howard via swift-corelibs-dev
>>> mailto:swift-corelibs-dev@swift.org>>
>>> To:Tony Parker via swift-corelibs-dev >> <mailto:swift-corelibs-dev@swift.
Luke Howard via swift-corelibs-dev
>> mailto:swift-corelibs-dev@swift.org>>
>> To: Tony Parker via swift-corelibs-dev > <mailto:swift-corelibs-dev@swift.org>>
>> Date:23/08/2016 08:55
>> Subject:Re: [swift-corelibs-dev] f8c3fe6c br
ibs-dev
>
> To:Tony Parker via swift-corelibs-dev
> Date: 23/08/2016 08:55
> Subject:Re: [swift-corelibs-dev] f8c3fe6c breaks on Darwin
> Sent by:swift-corelibs-dev-boun...@swift.org
>
>
>
> Also, the NSData test is broken on Darwin
v
To: Tony Parker via swift-corelibs-dev
Date: 23/08/2016 08:55
Subject:Re: [swift-corelibs-dev] f8c3fe6c breaks on Darwin
Sent by:swift-corelibs-dev-boun...@swift.org
Also, the NSData test is broken on Darwin when libdispatch is enabled –
possibly the system DispatchData is
Also, the NSData test is broken on Darwin when libdispatch is enabled –
possibly the system DispatchData is being pulled in and something funny
happens, this seems to work around it but I’m not sure if it is the correct fix:
+++ b/Foundation/NSData.swift
@@ -228,7 +228,7 @@ open class NSData : N
Enabling libdispatch seems to break the tests on Darwin because
DEPLOYMENT_ENABLE_LIBDISPATCH is not added to the XCode project build flags
(both for the C/Swift compilers).
--
www.lukehoward.com
soundcloud.com/lukehoward___
swift-corelibs-dev mailing
