<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">In response to feedback, I've revised SE-0138, now named UnsafeRawBufferPointer, and extended the review period by one week, through September 14.</div><div class=""><br class=""></div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsaferawbufferpointer.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsaferawbufferpointer.md</a></div><div class=""><br class=""></div><div class="">-Andy</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Sep 1, 2016, at 3:18 PM, Andrew Trick <<a href="mailto:atrick@apple.com" class="">atrick@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I’m resending this for Review Manager Dave A. because the announce list is dropping his messages...</div><div class=""><br class=""></div>Hello Swift community,<br class=""><br class="">The review of "UnsafeBytes" begins now and runs through September<br class="">7th. This late addition to Swift 3 is a follow-up to SE-0107:<br class="">UnsafeRawPointer. It addresses common use cases for UnsafeRawPointer,<br class="">allowing developers to continue working with collections of UInt8 values,<br class="">but now doing so via a type safe API. The UnsafeBytes API will not require <br class="">direct manipulation of raw pointers or reasoning about binding memory.<br class=""><br class="">The proposal is available here:<br class=""><br class=""> <<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsafebytes.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsafebytes.md</a>><br class=""><br class="">Reviews are an important part of the Swift evolution process. All reviews<br class="">should be sent to the swift-evolution mailing list at<br class=""><br class=""> <<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a>><br class=""><br class="">or, if you would like to keep your feedback private, directly to the<br class="">review manager. When replying, please try to keep the proposal link at<br class="">the top of the message:<br class=""><br class="">Proposal link:<br class=""> <<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a>><br class=""><br class="">What goes into a review?<br class=""><br class="">The goal of the review process is to improve the proposal under review<br class="">through constructive criticism and, eventually, determine the direction of<br class="">Swift. When writing your review, here are some questions you might want to<br class="">answer in your review:<br class=""><br class=""> * What is your evaluation of the proposal?<br class=""> * Is the problem being addressed significant enough to warrant a<br class=""> change to Swift?<br class=""> * Does this proposal fit well with the feel and direction of Swift?<br class=""> * If you have used other languages or libraries with a similar<br class=""> feature, how do you feel that this proposal compares to those?<br class=""> * How much effort did you put into your review? A glance, a quick<br class=""> reading, or an in-depth study?<br class=""><br class="">More information about the Swift evolution process is available at<br class=""><br class=""> <<a href="https://github.com/apple/swift-evolution/blob/master/process.md" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a>><br class=""><br class="">Thank you,<br class=""><br class="">-Dave Abrahams<br class="">Review Manager</div>_______________________________________________<br class="">swift-evolution-announce mailing list<br class=""><a href="mailto:swift-evolution-announce@swift.org" class="">swift-evolution-announce@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution-announce<br class=""></div></blockquote></div><br class=""></body></html>