averello/swift-mirror
1
0
Fork 0
mirror of https://github.com/apple/swift.git synced 2025-12-14 20:36:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

Apply changes from editorial review.

Browse Source
This commit is contained in:
Chris Adamson
2021-12-14 09:51:32 -05:00
parent 7beecc0600
commit a3a3ff1bdc
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
stdlib/public/core/MutableCollection.swift
View File

@@ -200,13 +200,13 @@ where SubSequence: MutableCollection
/// contiguous mutable storage of the entire collection. If no such storage
/// exists, the collection creates it. If the collection doesn't support an
/// internal representation in the form of contiguous mutable storage, this
/// method doesn't call `body` but instead immediately returns `nil`.
/// method doesn't call `body` --- it immediately returns `nil`.
///
/// The optimizer can often eliminate bounds- and uniqueness-checking
/// within an algorithm. When that fails, however, invoking the same
/// algorithm on the `buffer` argument may let you trade safety for speed.
///
/// Your closure should always perform any necessary cleanup, because the
/// Always perform any necessary cleanup in the closure, because the
/// method makes no guarantees about the state of the collection if the
/// closure throws an error. Your changes to the collection may be absent
/// from the collection after throwing the error, because the closure could
@@ -215,7 +215,7 @@ where SubSequence: MutableCollection
///
/// - Warning: Your `body` closure must not replace `buffer`. This leads
/// to a crash in all implementations of this method within the standard
/// library
/// library.
///
/// Successive calls to this method may provide a different pointer on each
/// call. Don't store `buffer` outside of this method.

8
stdlib/public/core/Sequence.swift
View File

@@ -387,10 +387,10 @@ public protocol Sequence {
/// Executes a closure on the sequence’s contiguous storage.
///
/// This method calls `body(buffer)`, where `buffer` is a pointer to the
/// collection’s contiguous storage. If no such storage exists, the collection
/// creates it. If the collection doesn’t support an internal representation
/// in a form of contiguous storage, the method doesn’t call `body` but
/// instead immediately returns `nil`.
/// collection’s contiguous storage. If the contiguous storage doesn't exist,
/// the collection creates it. If the collection doesn’t support an internal
/// representation in a form of contiguous storage, the method doesn’t call
/// `body` --- it immediately returns `nil`.
///
/// The optimizer can often eliminate bounds- and uniqueness-checking
/// within an algorithm. When that fails, however, invoking the same