Merge pull request #1541 from glessard/with-memory-rebound

[SE-0333] Mark as implemented

Author: glessard

proposals/0333-with-memory-rebound.md

@@ -3,22 +3,19 @@
 * Proposal: [SE-0333](0333-with-memory-rebound.md)
 * Authors: [Guillaume Lessard](https://github.com/glessard), [Andrew Trick](https://github.com/atrick)
 * Review Manager: [Ben Cohen](https://github.com/airspeedswift)
-* Status: **Awaiting implementation**
+* Status: **Implemented (Swift 5.7)**
 * Decision Notes: [Acceptance](https://forums.swift.org/t/54699)
-* Implementation: [draft pull request][draft-pr]
+* Implementation: [apple/swift#39529](https://github.com/apple/swift/pull/39529)
 * Bugs: [SR-11082](https://bugs.swift.org/browse/SR-11082), [SR-11087](https://bugs.swift.org/browse/SR-11087)
 
-[draft-pr]: https://github.com/apple/swift/pull/39529
-[pitch-thread]: https://forums.swift.org/t/pitch-expand-usability-of-withmemoryrebound/52500
-
 ## Introduction
 
 The function `withMemoryRebound(to:capacity:_ body:)`
 executes a closure while temporarily binding a range of memory to a different type than the callee is bound to.
 We propose to lift some notable limitations of `withMemoryRebound` and enable rebinding to a larger set of types,
 as well as rebinding the memory pointed to by raw memory pointers and buffers.
 
-Swift-evolution threads: [Pitch thread][pitch-thread], [Review thread](https://forums.swift.org/t/53799)
+Swift-evolution threads: [Pitch thread](https://forums.swift.org/t/52500), [Review thread](https://forums.swift.org/t/53799)
 
 ## Motivation
 
@@ -263,8 +260,6 @@ extension UnsafeMutableRawBufferPointer {
 
 ## Detailed design
 
-Note: please see the [draft PR][draft-pr] to visualize the proposed changes rather than the proposed final state.
-
 ```swift
 extension UnsafePointer {
   /// Executes the given closure while temporarily binding memory to