> On May 12, 2016, at 9:57 PM, Chris Lattner via swift-dev > <swift-dev@swift.org> wrote: > > >> On May 12, 2016, at 9:16 PM, Russ Bishop <xen...@gmail.com >> <mailto:xen...@gmail.com>> wrote: >> >> >>> On May 12, 2016, at 8:33 AM, Joe Groff <jgr...@apple.com >>> <mailto:jgr...@apple.com>> wrote: >>> >>> We might want to wait till we review Andy's UnsafeBytePointer proposal. If >>> we accept that, it will separate UnsafePointer<Void> into its own type. >>> >>> -Joe >> >> >> Fair enough; I can hold off on this branch until then. > > I’d suggest wrapping up this proposal as specified. When/if Andy’s proposal > goes through, we can move these APIs over. This proposal is progress from > the status quo, perfection is the enemy of good after all.
That’s the right call. For the record, I suggested moving to/fromOpaque to initializers during the community review and it was immediately shot down by Jordan because it’s incorrect for UnsafePointer<T> where T is non-Void. -Andy
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
