Skip to content

Commit 929dc0f

Browse files
phauslerr3econ
andauthored
More typo fixes
Co-authored-by: r3econ <505054+r3econ@users.noreply.github.com>
1 parent 15da3f9 commit 929dc0f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Evolution/NNNN-share.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ There are many other use cases that have been requested for this family of algor
1414

1515
## Proposed solution
1616

17-
AsyncAlgorithms will introduce a new extension function on AsyncSequence that will provide a shareable asynchronous sequence that will produce the same values upon iteration from multiple instances of it's AsyncIterator. Those iterations can take place in multiple isolations.
17+
AsyncAlgorithms will introduce a new extension function on AsyncSequence that will provide a shareable asynchronous sequence that will produce the same values upon iteration from multiple instances of its AsyncIterator. Those iterations can take place in multiple isolations.
1818

1919
When values from a differing isolation cannot be coalesced, the two options available are either awaiting (an exertion of back-pressure across the sequences) or buffering (an internal back-pressure to a buffer). Replaying the values from the beginning of the creation of the sequence is a distinctly different behavior that should be considered a different use case. This then leaves the behavioral characteristic of this particular operation of share as; sharing a buffer of values started from the initialization of a new iteration of the sequence. Control over that buffer should then have options to determine the behavior, similar to how AsyncStream allows that control. It should have options to be unbounded, buffering the oldest count of elements, or buffering the newest count of elements.
2020

0 commit comments

Comments
 (0)