[swift-evolution] [swift-evolution-announce] [Review] SE-0017: Change Unmanaged to use UnsafePointer

Kevin Ballard kevin at sb.org
Tue May 3 01:28:55 CDT 2016

On Thu, Apr 28, 2016, at 11:10 AM, Chris Lattner wrote:
> Hello Swift community,
> The review of "SE-0017: Change Unmanaged to use UnsafePointer" begins now and runs through May 3. The proposal is available here:
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0017-convert-unmanaged-to-use-unsafepointer.md
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 	https://lists.swift.org/mailman/listinfo/swift-evolution
> or, if you would like to keep your feedback private, directly to the review manager.
> What goes into a review?
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
> 	* What is your evaluation of the proposal?


> 	* Is the problem being addressed significant enough to warrant a change to Swift?

Yes. Going through COpaquePointer is quite annoying when dealing with Unmanaged and C context pointers.

> 	* Does this proposal fit well with the feel and direction of Swift?


> 	* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

A quick reading, and I've hit this pain point in my own code before.

-Kevin Ballard

More information about the swift-evolution mailing list