[swift-evolution] [Draft proposal] Faster/lower-level external String initialization

Max Moiseev moiseev at apple.com
Wed Jan 13 11:32:36 CST 2016

> On Jan 13, 2016, at 1:14 AM, Zach Waldowski <zach at waldowski.me> wrote:
> I might've mis-parsed the meaning of "'deprecation' magic". What's the
> best path forward in the near-term? Would `decodeCString` be the only
> one that becomes generic? Or, phrased differently, should there still be
> `UnsafePointer<CChar>`+`strlen` versions?

Sorry for not being clear. This is a breaking API change, and I think it would be nice of us to keep existing API in place marking it as deprecated for Swift 2.2 and later remove it in Swift 3. Here is an example <https://github.com/apple/swift/blob/master/stdlib/public/core/Index.swift#L76> of what I meant by ‘deprecation magic’.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160113/27b742b9/attachment.html>

More information about the swift-evolution mailing list