<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 2, 2016, at 1:34 PM, Tony Parker <<a href="mailto:anthony.parker@apple.com" class="">anthony.parker@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Arguments of being out of time do not compel me, personally. Introducing a new type is effectively permanent. We just got started with introducing Swift API. I don’t want to accidentally saddle ourselves with additional complexity forever without giving ourselves an adequate opportunity to fully consider what the right long-term solution is. The fact that you’ve already described the mismatch between struct Data and this type as “unfortunate” sounds, to me, like a big problem.</div></div></blockquote></div><br class=""><div class="">There is no mismatch between Data and UnsafeBytes. Data requires UnsafeBytes whenever the user is working with UnsafeRawPointers. UnsafeBytes is meant to enable interoperability with Data in these cases.</div><div class=""><br class=""></div><div class="">I included the Framework Interfaces section so that you could see what I think right long term solution is:</div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsafebytes.md#framework-interfaces" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0138-unsafebytes.md#framework-interfaces</a></div><div class=""><br class=""></div><div class="">If you have any concrete concerns about that long-term solution, then that would be good raise.</div><div class=""><br class=""></div><div class="">-Andy</div><div class=""><br class=""></div></body></html>