[swift-dev] What do to when stdlib guidelines conflict with proposal?

Russ Bishop xenadu at gmail.com
Wed May 11 16:53:48 CDT 2016

I’m implementing SE-0017 but based on the standard library guidelines I think Unmanaged should have initializers that take UnsafePointer/UnsafeMutablePointer and vice-versa which would fit more naturally with the way other conversions work. 

A later commit already moved toOpaque to be an initializer on OpaquePointer. I would add convenience initializers to UnsafePointer as well.

Any objections to just implementing this as initializers and marking fromOpaque as deprecated? I’m not sure how strict we should be in sticking to the proposal.


More information about the swift-dev mailing list