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

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

[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