Skip to content

Commit df4ff72

Browse files
authored
[SE-0314] Fix typo
The usage of "`AsyncSeries`" looks like a typo. The term doesn't appear anywhere else in the document. The document does use the word "series" a few times as an alternative to "stream", but using it as an identifier seems wrong. I replaced "`AsyncSeries`" with "`AsyncThrowingStream`" because it appears in the section on `AsyncThrowingStream`. Replacing it with "`AsyncStream`" would also work, but since this section is about the throwing variant, `AsyncThrowingStream` seems better.
1 parent 23823bb commit df4ff72

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

proposals/0314-async-stream.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ Alternatively if a source is just an async function (one that represents a backp
135135

136136
### Creating an `AsyncThrowingStream`
137137

138-
Along with the potentially infinite sequence in the example above, `AsyncSeries` can also adapt APIs like the slightly contrived one below. The `findVegetables` function uses callback closures that are called with each retrieved vegetable, as well as when the vegetables have all been returned or an error occurs.
138+
Along with the potentially infinite sequence in the example above, `AsyncThrowingStream` can also adapt APIs like the slightly contrived one below. The `findVegetables` function uses callback closures that are called with each retrieved vegetable, as well as when the vegetables have all been returned or an error occurs.
139139

140140
```swift
141141
func buyVegetables(

0 commit comments

Comments
 (0)