Re: [swift-corelibs-dev] Building Foundation in Xcode

Hey Brian, So I was able to get a toolchain for OSX and everything seemed to work. But now I'm trying to test my changes on Linux and it seems my changes are halting the tests when I run ninja test in the Foundation directory. I began this discussion on a pull request

Re: [swift-corelibs-dev] Wrong type in NSHTTPURLResponse

On 15 Mar 2016, at 16:16, Daniel Eggert via swift-corelibs-dev wrote: > > The allHeaderFields in > > public class NSHTTPURLResponse : NSURLResponse { >[...] >public let allHeaderFields: [NSObject : AnyObject] > } > > should have been [String : String] >

Re: [swift-corelibs-dev] Cannot call CFStreamCreatePairWithSocket on Linux

Hi Pushkar, Yes, this is used by “getStreamsToHostWithName”. I think we’ll have to come up with a replacement implementation here, either by starting with the old CFNetwork open source code or writing our own. - Tony > On Mar 15, 2016, at 8:00 AM, Pushkar N Kulkarni via swift-corelibs-dev >

Re: [swift-corelibs-dev] Internal Tests

Using @testable makes sense to me. Let's try it out. - Tony > On Mar 15, 2016, at 7:54 AM, Robert Stephen Thompson via swift-corelibs-dev > wrote: > > If it doesn’t use it on Linux, it’s because I was mostly running tests in > Xcode heh, and didn’t end up

Re: [swift-corelibs-dev] Internal Tests

If it doesn’t use it on Linux, it’s because I was mostly running tests in Xcode heh, and didn’t end up needing it in the end. On Linux, of course, I think you’d want @testable import Foundation. I’m not an Apple guy, though, I just happen to be the guy who wrote TestNSXMLDocument.swift! So if

Re: [swift-corelibs-dev] NSURLSession & libcurl

That seems pretty reasonable to me, I guess the only thing to watch out for is private vs internal. Sent from my iPhone > On Mar 15, 2016, at 2:44 AM, Daniel Eggert wrote: > > Is it ok for me to split the libcurl specific code inside Foundation into a > separate file,

Re: [swift-corelibs-dev] NSURLSession & libcurl

Is it ok for me to split the libcurl specific code inside Foundation into a separate file, say NSURLSession+curl.swift ? Or should I try to keep everything inside NSURLSession.swift ? If I go for a separate file, I'd be able to differentiate between internal and private for the helpers. I'll

Re: [swift-corelibs-dev] KVC dependent classes

Sorry, I said NSProgress but I meant NSPredicate. I personally can't even imagine what a alternative API for NSPredicate would look like 樂 > On 15 Mar 2016, at 00:21, Tony Parker wrote: > > Hi David, > > It’s likely that we’ll have to come up with some alternative