Skip to content

Commit 4a7ac28

Browse files
committed
Remove stray spaces
These looks like the side effect of a find-and-replace for PR 82558 fixing 'cancelled' vs 'canceled'.
1 parent fe6a8fa commit 4a7ac28

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

stdlib/public/Concurrency/DiscardingTaskGroup.swift

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ public struct DiscardingTaskGroup {
205205
/// If you add a task to a group after canceling the group,
206206
/// that task is canceled immediately after being added to the group.
207207
///
208-
/// Immediately canceled child tasks should therefore cooperatively check for and
208+
/// Immediately canceled child tasks should therefore cooperatively check for and
209209
/// react to cancellation, e.g. by throwing an `CancellationError` at their
210210
/// earliest convenience, or otherwise handling the cancellation.
211211
///
@@ -427,7 +427,7 @@ public func _unsafeInheritExecutor_withThrowingDiscardingTaskGroup<GroupResult>(
427427
///
428428
/// - when ``cancelAll()`` is invoked on it,
429429
/// - when an error is thrown out of the `withThrowingDiscardingTaskGroup { ... }` closure,
430-
/// - when the ``Task`` running this task group is canceled .
430+
/// - when the ``Task`` running this task group is canceled.
431431
///
432432
/// But also, and uniquely in *discarding* task groups:
433433
/// - when *any* of its child tasks throws.
@@ -436,7 +436,7 @@ public func _unsafeInheritExecutor_withThrowingDiscardingTaskGroup<GroupResult>(
436436
/// whenever *any* child task throws an error is a behavior unique to discarding task groups,
437437
/// because achieving such semantics is not possible otherwise, due to the missing `next()` method
438438
/// on discarding groups. Accumulating task groups can implement this by manually polling `next()`
439-
/// and deciding to `cancelAll()` when they decide an error should cause the group to become canceled,
439+
/// and deciding to `cancelAll()` when they decide an error should cause the group to become canceled,
440440
/// however a discarding group cannot poll child tasks for results and therefore assumes that child
441441
/// task throws are an indication of a group wide failure. In order to avoid such behavior,
442442
/// use a ``DiscardingTaskGroup`` instead of a throwing one, or catch specific errors in
@@ -447,7 +447,7 @@ public func _unsafeInheritExecutor_withThrowingDiscardingTaskGroup<GroupResult>(
447447
/// tasks).
448448
///
449449
/// A canceled task group can still keep adding tasks, however they will start
450-
/// being immediately canceled, and may act accordingly to this. To avoid adding
450+
/// being immediately canceled, and may act accordingly to this. To avoid adding
451451
/// new tasks to an already canceled task group, use ``addTaskUnlessCancelled(priority:body:)``
452452
/// rather than the plain ``addTask(priority:body:)`` which adds tasks unconditionally.
453453
///

0 commit comments

Comments
 (0)