Re: [swift-corelibs-dev] CChar vs Int8

OK, I filed [SR-466] as a compiler issue. If the behaviour changes and that flows through to Darwin Foundation, we can update the open source one... — Luke > On 5 Jan 2016, at 8:21 AM, Philippe Hausler wrote: > > No C strings import as UnsafePointer for some reason; they all import > as Int8

Re: [swift-corelibs-dev] CChar vs Int8

No C strings import as UnsafePointer for some reason; they all import as Int8 e.g. public func pthread_setname_np(_: UnsafePointer) -> Int32 > On Jan 4, 2016, at 1:20 PM, Tony Parker via swift-corelibs-dev > wrote: > > Hi Luke, > >> On Jan 2, 2016, at 8:28 PM, Luke Howard via swift-corelibs

Re: [swift-corelibs-dev] CChar vs Int8

Hi Luke, > On Jan 2, 2016, at 8:28 PM, Luke Howard via swift-corelibs-dev > wrote: > > Many Foundation APIs use Int8 instead of CChar when representing C strings, > e.g.: > var UTF8String: UnsafePointer >

[swift-corelibs-dev] CChar vs Int8

Many Foundation APIs use Int8 instead of CChar when representing C strings, e.g.: var UTF8String: UnsafePointer https://developer.apple.com