On Tue, Dec 15, 2015, at 03:03 PM, Joe Groff via swift-dev wrote: > > Yeah, it seems to me like a reasonable refinement for 'withUnsafePointer' to > take an immutable parameter. Since this is a stdlib API change, you should > suggest that on swift-evolution.
A change like that is going to break any code that relies on the inout optimization (where it uses call-by-reference instead of copy-in copy-out when possible). Yes, such code is in violation of Swift semantics today, but it does work. -Kevin Ballard _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
