<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi swift-evolutionaries,</div><div class=""><br class=""></div><div class="">I'm sorry to bring a proposal late to the table, but this could make a big difference to the Swift 3 migration experience.</div><div class=""><br class=""></div><div class="">This proposal adds basic usability for working with raw memory without breaking source. The need to provide higher level API for working with raw memory buffers has always been evident, but making improvements in this area depended on first introducing `UnsafeRawPointer`. It was not clear until the final week of source-breaking changes whether SE-0107 would make it into Swift 3. Now that it has, we should use the little remaining time to improve the migration experience and encourage correct use of the memory model by introducing a low-risk additive API.</div><div class=""><br class=""></div><div class="">Proposal:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/atrick/swift-evolution/blob/unsafebytes/proposals/NNNN-UnsafeBytes.md" class="">https://github.com/atrick/swift-evolution/blob/unsafebytes/proposals/NNNN-UnsafeBytes.md</a></div><div class=""><br class=""></div><div class=""></div></body></html>