Skip to content

NFC: Rename OutputByteStream to WritableByteStream for a more semantic meaning of the type. #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 17, 2020

Conversation

sergiocampama
Copy link
Contributor

This just replaces the OutputByteStream type name with WritableByteStream. The implementation classes of this protocol were not renamed to avoid messing with the types too much, and a OutputByteBuffer typealias was added to prevent breakages because of this change.

@neonichu
Copy link
Contributor

Seems more confusing to me to have two names for the same type? 🤔

@sergiocampama
Copy link
Contributor Author

Seems more confusing to me to have two names for the same type? 🤔

The type alias should be temporary, or do you think I can remove it and force update on clients when they adopt the new version?

@neonichu
Copy link
Contributor

Ah, OK, it wasn't clear to me that this is supposed to be temporary, then it seems fine to me.

@neonichu
Copy link
Contributor

@swift-ci please test

@sergiocampama sergiocampama merged commit 0e32e38 into swiftlang:master Sep 17, 2020
compnerd added a commit to compnerd/swift-tools-support-core that referenced this pull request Sep 17, 2020
The file was misnamed but was not caught during review.  This fixes the
file name to repair the build.
compnerd added a commit that referenced this pull request Sep 17, 2020
TSCBasic: repair build after #125
@sergiocampama sergiocampama deleted the output branch September 24, 2020 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants