New and Improved io.Stream
interface
#2584
Merged
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.
This is a big change which changes the
io.Stream
interface from being a hybrid inheritance model (pointer-to-vtable + data) to a flat model (procedure-value + data) which is more akin to aruntime.Allocator
.The number of stream "modes" has been greatly reduced to remove unnecessary and confusing options:
The
io.Writer
etc types are now just aliases ofio.Stream
rather than being distinct data types.In
core:os/os2
, theFile
type now uses theio.Stream
internally for its general operations meaning a stream can pretend to be a file if necessary (similar toopen_memstream
).