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

Jacob Bandes-Storch jtbandes at gmail.com
Wed May 11 18:33:35 CDT 2016

+1 from the proposal author, although since it went through community
review that doesn't make me an authority ;)
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.
> Russ
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20160511/8afd75c1/attachment.html>

More information about the swift-dev mailing list