> On Sep 1, 2017, at 10:27 PM, Douglas Gregor via swift-evolution > <[email protected]> wrote: > > Hello Swift community, > > The review of SE-0184 "Unsafe[Mutable][Raw][Buffer]Pointer: add missing > methods, adjust existing labels for clarity, and remove deallocation size" > begins now and runs through September 7, 2017. The proposal is available here: > > https://github.com/apple/swift-evolution/blob/master/proposals/0184-unsafe-pointers-add-missing.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0184-unsafe-pointers-add-missing.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 > <https://lists.swift.org/mailman/listinfo/swift-evolution> > or, if you would like to keep your feedback private, directly to the review > manager. When replying, please try to keep the proposal link at the top of > the message: > > Proposal link: > > https://github.com/apple/swift-evolution/blob/master/proposals/0184-unsafe-pointers-add-missing.md > > <https://github.com/apple/swift-evolution/blob/master/proposals/0184-unsafe-pointers-add-missing.md> > Reply text > Other replies > > <https://github.com/apple/swift-evolution/pulls#what-goes-into-a-review-1>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? +1.
> Is the problem being addressed significant enough to warrant a change to > Swift? I use the affected constructs every day, and without this proposal using them correctly and safely requires working around a lot of missing API surface area. This will allow me to clean up my code significantly. > Does this proposal fit well with the feel and direction of Swift? It is a logical extension of the UnsafePointer and UnsafeBufferPointer model, allowing many existing operations on UnsafePointer to be performed directly on UnsafeBufferPointer. > If you have used other languages or libraries with a similar feature, how do > you feel that this proposal compares to those? N/A > How much effort did you put into your review? A glance, a quick reading, or > an in-depth study? I did a in-depth review of an earlier draft. I did a quick read of this final one. > More information about the Swift evolution process is available at > > https://github.com/apple/swift-evolution/blob/master/process.md > <https://github.com/apple/swift-evolution/blob/master/process.md> > Thank you, > > -Doug > > Review Manager > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
