[swift-evolution] SE-0138 UnsafeRawBufferPointer
me at benrimmington.com
Sun Sep 11 05:07:28 CDT 2016
> On 11 Sep 2016, at 01:53, Andrew Trick wrote:
> The review period has been extended until September 14. The UnsafeRawBufferPointer type name is settled, but we still need to come up with an answer for the name of the new closure taking functions:
> withXyz() should normally reveal the closure argument type as Xyz. That's why I originally proposed UnsafeBytes as the type name. Now that we've decided to use the descriptive type instead we have a problem...
Does the `enumerateBytes` method (of Foundation.Data and DispatchData) also need an UnsafeRawBufferPointer version?
More information about the swift-evolution