Skip to content
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

refactor: Refactor oio::Write by accepting oio::Reader instead #3008

Merged
merged 6 commits into from
Sep 6, 2023

Conversation

Xuanwo
Copy link
Member

@Xuanwo Xuanwo commented Sep 5, 2023

No description provided.

Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Signed-off-by: Xuanwo <github@xuanwo.io>
Copy link
Member

@silver-ymz silver-ymz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Xuanwo Xuanwo merged commit 43d0327 into main Sep 6, 2023
91 checks passed
@Xuanwo Xuanwo deleted the refactor-writer branch September 6, 2023 03:30
@suyanhanx
Copy link
Member

I think this change is good, but the renaming is unacceptable. Although it changes the acceptable type of the content, it does not align with the general concept of a pipe, which involves data transmission/ communication as a pipe.It remains a sink,performing the final consumption action. This renaming makes the modification difficult to accept without a rfc or issue for discussion.

@Xuanwo
Copy link
Member Author

Xuanwo commented Sep 6, 2023

It remains a sink,performing the final consumption action.

sink is not a good name here since it's widely used in rust streaming related ecosystem. I will start a new PR to address this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants