Apply suggestions from code review

Co-authored-by: Ben Rimmington <[email protected]>

Author: grynspan

proposals/NNNN-temporary-buffers.md

@@ -124,7 +124,11 @@ A new free function would be introduced in the Standard Library:
 /// the buffer) must not escape—it will be deallocated when `body` returns and
 /// cannot be used afterward.
 @_transparent
-public func withUnsafeUninitializedMutableBufferPointer<T, R>(to type: T.Type, capacity: Int, _ body: (UnsafeMutableBufferPointer<T>) throws -> R) rethrows -> R
+public func withUnsafeUninitializedMutableBufferPointer<T, R>(
+  to type: T.Type,
+  capacity: Int,
+  _ body: (UnsafeMutableBufferPointer<T>) throws -> R
+) rethrows -> R
 ```
 
 We could optionally provide additional free functions for dealing with a raw buffer or a pointer to a single value. All of the proposed functions can be layered atop each other, so only one underlying implementation is ultimately needed:
@@ -162,7 +166,11 @@ We could optionally provide additional free functions for dealing with a raw buf
 /// the buffer) must not escape—it will be deallocated when `body` returns and
 /// cannot be used afterward.
 @_transparent
-public func withUnsafeUninitializedMutableRawBufferPointer<R>(byteCount: Int, alignment: Int, _ body: (UnsafeMutableRawBufferPointer) throws -> R) rethrows -> R
+public func withUnsafeUninitializedMutableRawBufferPointer<R>(
+  byteCount: Int,
+  alignment: Int,
+  _ body: (UnsafeMutableRawBufferPointer) throws -> R
+) rethrows -> R
 
 /// Provides scoped access to a pointer to memory of the specified type.
 ///
@@ -187,7 +195,10 @@ public func withUnsafeUninitializedMutableRawBufferPointer<R>(byteCount: Int, al
 /// The pointer passed to `body` must not escape—it will be deallocated when
 /// `body` returns and cannot be used afterward.
 @_transparent
-public func withUnsafeUninitializedMutablePointer<T, R>(to type: T.Type, _ body: (UnsafeMutablePointer<T>) throws -> R) rethrows -> R
+public func withUnsafeUninitializedMutablePointer<T, R>(
+  to type: T.Type,
+  _ body: (UnsafeMutablePointer<T>) throws -> R
+) rethrows -> R
 ```
 
 Note the functions are marked `@_transparent` to ensure they are emitted into the calling frame. This is consistent with the annotations on most other pointer manipulation functions.