[swift-dev] What do to when stdlib guidelines conflict with proposal?
atrick at apple.com
Fri May 13 15:16:15 CDT 2016
> On May 12, 2016, at 9:57 PM, Chris Lattner via swift-dev <swift-dev at swift.org> wrote:
>> On May 12, 2016, at 9:16 PM, Russ Bishop <xenadu at gmail.com <mailto:xenadu at gmail.com>> wrote:
>>> On May 12, 2016, at 8:33 AM, Joe Groff <jgroff at apple.com <mailto:jgroff at 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.
>> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-dev