9 replies and sub-replies as of Jun 21 2016

No idea, you'd want to ping the Foundation people.
Who could I ping? (I have no idea who’s working on Foundation) Thank you anyways ;)
it can fail in large allocations. Normally we don’t claim nil for malloc failure but this is to prevent silliness
What kind of silliness?
like users passing in unreasonably large integers
That seems more like programmer error than a recoverable condition. Array would trap in such cases.
it is, but it would then diverge the behavior of the reference type of NSData
Thank you for clarifying! I solved the problem with Data(bytesNoCopy: …) and custom deallocator which invokes `free`