-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update to bytes 1.0 #4
Conversation
for x in data.iter_mut() { | ||
*x.as_mut_ptr() = 0; | ||
for i in 0..data.len() { | ||
data.write_byte(i, 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe instead of that we can do something with bytes::buf::UninitSlice
here without having to initialize everything first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me otherwise, that can also be done in a separate PR IMHO.
Cargo.toml
Outdated
@@ -12,4 +12,4 @@ documentation = "https://docs.rs/input_buffer/0.3.1" | |||
version = "0.3.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIU this changes the API so the next release should be 0.4.0
@application-developer-DA is there anything blocking this PR from being merged? There's a few upstream crates depending on it so would be great if we could get it in / release. Thank you! |
Thank you @application-developer-DA. Do you also mind releasing 0.4.0 to crates? |
Sure. @agalakhov , could you please publish it? (or give me permissions to do so, I'm not an owner of the crate ;) |
Bump @agalakhov it'd be great if you could do the release / give DA perms! Thank you again. |
No description provided.