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
On 15 Mar 2016, at 16:16, Daniel Eggert via swift-corelibs-dev
<swift-corelibs-dev@swift.org> wrote:
>
> The allHeaderFields in
>
> public class NSHTTPURLResponse : NSURLResponse {
>[...]
>public let allHeaderFields: [NSObject : AnyObject]
> }
>
>
Ok.
That test case fail on OS X, though. Should I open a bug?
/Daniel
> On Mar 28, 2016, at 22:17, Philippe Hausler wrote:
>
> DEPLOYMENT_ENABLE_LIBDISPATCH should not be enabled unless you specifically
> enable it (this is until we get libdispatch fully integrated into
This is on OS X will everything pulled from master yesterday. I'm using Xcode,
and I built a toolchain from source. Same happens with the 2016-03-24 toolchain
from swift.org.
For some reason DEPLOYMENT_ENABLE_LIBDISPATCH isn't set, but I guess it should
be?
/Daniel
> On 26 Mar 2016, at
Changes since last week:
NSURLSessionDataTask (i.e. GET requests) now work with callbacks and with
completion handler.
Debug output is enabled by environment variables.
Handling a few common error scenarios to return the corresponding NSError.
/Daniel
> On 08 Apr 2016, at 01:44, Daniel Dunbar <daniel_dun...@apple.com> wrote:
>
>>
>> On Apr 7, 2016, at 10:15 AM, Daniel Eggert via swift-corelibs-dev
>> <swift-corelibs-dev@swift.org> wrote:
>>
>> With this being merged
>>
>>
On 08 Apr 2016, at 16:52, Tony Parker wrote:
>
> These are turbulent times for syntax in Swift. :)
>
> Pretty soon now we're also going to have to deal with the swift renaming
> rules as applied to all functions in corelibs-foundation.
>
> - Tony
I know. Trying to
> On 14 Mar 2016, at 18:29, Robert Stephen Thompson
> wrote:
>
> Just a couple of tips based on my experience wrapping libxml2 for
> NSXMLDocument:
> 1. You’ll need to actually import and link libcurl with CoreFoundation
> instead of trying to make a
> On 28 Mar 2016, at 23:59, Philippe Hausler wrote:
>
> the swift-corelibs-foundation compiled for Darwin does not define that yet
> either. Are you seeing issues with it when defined?
When I add
OTHER_SWIFT_FLAGS = -DDEPLOYMENT_ENABLE_LIBDISPATCH
it works. So I guess
> On 31 Mar 2016, at 21:44, Tony Parker wrote:
>
> Hi Zach, Daniel,
>
>> On Mar 31, 2016, at 11:03 AM, Zach Waldowski via swift-corelibs-dev
>> wrote:
>>
>> The semantics of the methods are fairly nuanced in ObjC.
>>
>> You can have a
Is there interest in bridging between dispatch_data_t and NSData similar to
what's available with Darwin Foundation. Being able to avoid buffer copies
seems like a big win. And with libdispatch (almost) being available on Linux,
would it make sense to back (immutable) NSData with libdispatch in
mentation and contribute on top of it.
>>
>> Thanks!
>>
>> Pushkar N Kulkarni,
>> IBM Runtimes
>>
>> Simplicity is prerequisite for reliability - Edsger W. Dijkstra
>>
>>
>>
>> -----swift-corelibs-dev-boun...@swift.org wrote: -
Wouldn't it still be a huge win to use dispatch for reading from / writing to a
file descriptor?
/Daniel
> On Apr 18, 2016, at 01:52, Chris Bailey via swift-corelibs-dev
> wrote:
>
> Hi Dan:
>
> The Dispatch sources are mostly complete - unfortunately
>
n top of
>>> it.
>>>
>>> Thanks!
>>>
>>> Pushkar N Kulkarni,
>>> IBM Runtimes
>>>
>>> Simplicity is prerequisite for reliability - Edsger W. Dijkstra
>>>
>>>
>>>
>>> -swift-corelibs-dev-b
14 matches
Mail list logo