[swift-evolution] [swift-evolution-announce] [Review] SE-0107: UnsafeRawPointer API

[Robert Widmann]

> 	* What is your evaluation of the proposal?

+1 This is an excellent change to make a fragile and tricky part of the language more explicit and correct by design.

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

Yes

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

Yes

> 	* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

Raw memory access in languages with strong static type systems has typically come with some kind of marshalling framework or there is a virtual machine in place to ensure some measure of consistency with foreign pointers.  Because we can make no such guarantees, this proposal provides an excellent middle ground:  A new type to encapsulate and mark old semantics plus new typed means of access if desired.

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

Read the proposal a few times.

> On Jun 28, 2016, at 9:05 PM, Chris Lattner <clattner at apple.com> wrote:
> 
> Hello Swift community,
> 
> The review of “SE-0107: UnsafeRawPointer API” begins now and runs through July 4, 2016. The proposal is available here:
> 
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0107-unsaferawpointer.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 contribute to 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?
> 	* Does this proposal fit well with the feel and direction of Swift?
> 	* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> 	* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> 
> More information about the Swift evolution process is available at
> 
> 	https://github.com/apple/swift-evolution/blob/master/process.md
> 
> Thank you,
> 
> -Chris Lattner
> Review Manager
> 
> 
> _______________________________________________
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution-announce