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

cubic: use appropriate byte counting #624

Merged
merged 1 commit into from
Sep 16, 2020
Merged

cubic: use appropriate byte counting #624

merged 1 commit into from
Sep 16, 2020

Conversation

junhochoi
Copy link
Contributor

Implements quicwg/base-drafts#3917 for CUBIC.

@junhochoi junhochoi requested a review from a team as a code owner August 28, 2020 22:21
@junhochoi junhochoi changed the title cubic: use accurate byte counting cubic: use appropriate byte counting Aug 28, 2020
src/h3/ffi.rs Outdated Show resolved Hide resolved
@junhochoi junhochoi force-pushed the cubic_byte_counting branch 2 times, most recently from 0dc5d2a to 476598e Compare September 9, 2020 01:15
src/recovery/cubic.rs Outdated Show resolved Hide resolved
src/recovery/cubic.rs Outdated Show resolved Hide resolved
src/recovery/cubic.rs Outdated Show resolved Hide resolved
src/recovery/cubic.rs Outdated Show resolved Hide resolved
Copy link
Member

@ghedo ghedo left a comment

Choose a reason for hiding this comment

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

Added a few nits, though I haven't quite gotten my head around this change yet, so I'll need to do another pass later.

Also, I just realized I "misspelled" appropriate as accurate in the commit message for the Reno change 🤦‍♂️ Need to replace s/accurate/appropriate/ in the commit message in this PR.

@ghedo ghedo merged commit 72a2fe9 into master Sep 16, 2020
@ghedo ghedo deleted the cubic_byte_counting branch September 16, 2020 14:52
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