improve AbstractPipe docs and IOContext handling as an AbstractPipe #52768
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following some complains that
AbstractPipe
did not mention the functions that comprise its API, I have updated that and some other related details of its subtypes.IOContext{IO}(io)
to avoid excess specialization. Any explicitly set parameter should now be inherited by futureIOContext
constructions around it, rather than always directly adopting thetypeof(io.io)
type instead as the new parameter.