* Move platform requirements to availability annotations
Adding or raising the deployment platforms in the package manifest is a
SemVer major breaking change as consumers must also add or raise their
deployment platforms. This is a known limitation of SwiftPM.
Unforunately this means that it's very difficult for non-leaf packages
to adopt packages which declare their platforms in the manifest. Doing
so puts the brakes on adoption and ecosystem growth. For 'core' packages
like this one availability constraints should be expressed on
declarations rather than in the manifest.
This patch adds equivalent availability annotations to declarations
across the package and removes platforms from the package manifest.
* Address naming feedback
# Motivation
I raise on the pitch of `AsyncBufferedByteIterator` on the forums that I think the iterator must not be `Sendable`. The reasoning for this is twofold. First, an iterator is the connection of a consumer to the `AsyncSequence`; therefore, iterators should not be shared since it breaks that assumption. Secondly, the implementation of the `AsyncBufferedByteIterator` can be more straight forward since we don't have to check for unique ownership of the storage.
# Modification
Remove the `Sendable` conformances from `AsyncBufferedByteIterator`.
* slight adjustments to make docc rendering of AsyncBufferedByteIterator documentation nicer
* Apply suggestions from code review
Co-authored-by: Chris Adamson <invalidname@gmail.com>
Co-authored-by: Chris Adamson <invalidname@gmail.com>
* Add a performance tuned asynchronous iterator for creeating asynchronous byte sequences
* Some spelling fixes and language clarity improvements
* Add some more detail on the docs for the `AsyncBufferedByteIterator` initializer
* Move the storage to a usable from inline type