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

Dmitri Gribenko gribozavr at gmail.com
Wed May 11 18:50:55 CDT 2016

On Wed, May 11, 2016 at 2:53 PM, Russ Bishop via swift-dev
<swift-dev at swift.org> wrote:
> 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.

Unmanaged shall be redesigned.  We thought about this change, and
decided to go for the incremental change as proposed.  Bigger changes
should be considered as a part of a cohesive Unmanaged redesign.


(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/

More information about the swift-dev mailing list