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

2016-01-02 Thread Drew Crawford via swift-corelibs-dev
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

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

2016-01-02 Thread Keith Smiley via swift-corelibs-dev
There's a mention of this in the "Issues" document here: https://github.com/apple/swift-corelibs-foundation/blob/master/Docs/Issues.md#known-issues That makes it sound like this isn't meant to be a long term limitation: > In order to translate between these types, we have temporarily added a > p

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

2016-01-02 Thread Philippe Hausler via swift-corelibs-dev
String is bridged it just is not yet implicitly converted via the compiler; we are missing certain functionality due to the compiler not supporting the objc code paths on linux. The re-naming of swift classes exposed from Foundation will likely leave the class NSString still a thing (however it

[swift-corelibs-dev] relationship of CF

2016-01-02 Thread Drew Crawford via swift-corelibs-dev
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] relationship of CF

2016-01-02 Thread Philippe Hausler via swift-corelibs-dev
Responses inline: > On Jan 2, 2016, at 3:58 AM, Drew Crawford via swift-corelibs-dev > wrote: > > 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

Re: [swift-corelibs-dev] relationship of CF

2016-01-02 Thread Dave Fenton via swift-corelibs-dev
Given the educational angle that seems to be part of the mission of Swift, I was hoping that the Raspberry Pi port would be something the Swift project would directly integrate and distribute -david > On Jan 2, 2016, at 3:00 PM, Philippe Hausler via swift-corelibs-dev > wrote: > > > Respo

Re: [swift-corelibs-dev] relationship of CF

2016-01-02 Thread Philippe Hausler via swift-corelibs-dev
I think perhaps it might be worth something to investigate on what it would take to get these extra platforms integrated into CI as nodes to the Swift primary builders. As a note since we do target ARM as a primary platform for Darwin and we do target Linux as a primary platform, ARM linux is no

[swift-corelibs-dev] CChar vs Int8

2016-01-02 Thread Luke Howard via swift-corelibs-dev
Many Foundation APIs use Int8 instead of CChar when representing C strings, e.g.: var UTF8String: UnsafePointer https://developer.apple.com