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

fix: get rid of flush #1052

Merged
merged 1 commit into from
Jul 17, 2024
Merged

fix: get rid of flush #1052

merged 1 commit into from
Jul 17, 2024

Conversation

rgrinberg
Copy link
Member

We haven't yet released [Http] so it's ok to change things. It doesn't seem right to release the library with a deprecated feature.

It's easy enough to just drop this field in [Http]

Signed-off-by: Rudi Grinberg [email protected]

@rgrinberg rgrinberg requested a review from mseri June 27, 2024 21:39
Comment on lines 43 to 46
let make ?(version = `HTTP_1_1) ?(status = `OK) ?(flush = false)
?(encoding = Transfer.Chunked) ?(headers = Header.init ()) () =
ignore flush;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
let make ?(version = `HTTP_1_1) ?(status = `OK) ?(flush = false)
?(encoding = Transfer.Chunked) ?(headers = Header.init ()) () =
ignore flush;
let make ?(version = `HTTP_1_1) ?(status = `OK)
?(encoding = Transfer.Chunked) ?(headers = Header.init ()) () =

Why not dropping flush also from here?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think this would be a bigger breaking change. Since this make function has been around for a long time in many released versions. I'm honestly happy to get rid of it as well though if you prefer.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think at this point why not. Removing the flush field is already breaking, we may as well do it once and for all

Copy link
Contributor

Choose a reason for hiding this comment

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

If we're talking about the 6.0 major version upgrade, I think the point is precisely to allow API breakage? One has to do some cleanup at some point, and major versions are the only opportunity we have of doing so.

@rgrinberg rgrinberg force-pushed the ps/rr/fix__get_rid_of_flush branch from 300b29f to 651ef43 Compare June 28, 2024 22:22
We haven't yet released [Http] so it's ok to change things. It doesn't
seem right to release the library with a deprecated feature.

It's easy enough to just drop this field in [Http]

Signed-off-by: Rudi Grinberg <[email protected]>

<!-- ps-id: adbceded-c111-4ce6-8083-96c5a8a7ca26 -->
@rgrinberg rgrinberg force-pushed the ps/rr/fix__get_rid_of_flush branch from 651ef43 to 6101a53 Compare July 15, 2024 23:16
@rgrinberg
Copy link
Member Author

@mefyl do you want to have a look?

@mefyl
Copy link
Contributor

mefyl commented Jul 17, 2024

LGTM !

@rgrinberg rgrinberg merged commit abcad4c into master Jul 17, 2024
16 of 26 checks passed
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.

3 participants