[swift-evolution] [RFC] UnsafeBytePointer API for In-Memory Layout
glessard at tffenterprises.com
Mon May 9 14:57:32 CDT 2016
I’m sympathetic to the elimination of UnsafePointer<Void> as general shorthand for an arbitrary pointer, but I lose the plot of this very long proposal. It seems to me that this increases API surface, yet everything I could do before, I could still do; it just involves more typing. What exactly does this make better?
More information about the swift-evolution