+1 as well. I would love to have Data.withUnsafeBytes use this type, and I agree that UnsafeBytes and Data have orthogonal and not overlapping use cases.<br><div class="gmail_quote"><div dir="ltr">On Sat, Sep 3, 2016 at 08:59 gs. via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
<br>
I think that 'Unsafe' is fine because the mutable variant is definitely unsafe.<br>
<br>
I have some audio related code that would benefit greatly from this addition so I am all for it.<br>
<br>
TJ<br>
<br>
> On Sep 1, 2016, at 12:10, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
><br>
> Hello Swift community,<br>
><br>
> The review of "UnsafeBytes" begins now and runs through September<br>
> 7th. This late addition to Swift 3 is a follow-up to SE-0107:<br>
> UnsafeRawPointer. It addresses common use cases for UnsafeRawPointer,<br>
> allowing developers to continue working with collections of UInt8 values,<br>
> but now doing so via a type safe API. The UnsafeBytes API will not require<br>
> direct manipulation of raw pointers or reasoning about binding memory.<br>
><br>
> The proposal is available here:<br>
><br>
> <<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsafebytes.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsafebytes.md</a>><br>
><br>
> Reviews are an important part of the Swift evolution process. All reviews<br>
> should be sent to the swift-evolution mailing list at<br>
><br>
> <<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a>><br>
><br>
> or, if you would like to keep your feedback private, directly to the<br>
> review manager. When replying, please try to keep the proposal link at<br>
> the top of the message:<br>
><br>
> Proposal link:<br>
> <<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a>><br>
><br>
> What goes into a review?<br>
><br>
> The goal of the review process is to improve the proposal under review<br>
> through constructive criticism and, eventually, determine the direction of<br>
> Swift. When writing your review, here are some questions you might want to<br>
> answer in your review:<br>
><br>
> * What is your evaluation of the proposal?<br>
> * Is the problem being addressed significant enough to warrant a<br>
> change to Swift?<br>
> * Does this proposal fit well with the feel and direction of Swift?<br>
> * If you have used other languages or libraries with a similar<br>
> feature, how do you feel that this proposal compares to those?<br>
> * How much effort did you put into your review? A glance, a quick<br>
> reading, or an in-depth study?<br>
><br>
> More information about the Swift evolution process is available at<br>
><br>
> <<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a>><br>
><br>
> Thank you,<br>
><br>
> -Dave Abrahams<br>
> Review Manager<br>
> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>