-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
bytes 0.5 compatibility #42
Comments
captured.rs is still broken, see NLnetLabs#42 Signed-off-by: Fabian Grünbichler <[email protected]>
Just switching to |
Obviously you know your code base better than me, and I am happy if I don't have to dig in further and can leave it in your hands instead :) it will probably take at least a few weeks until this actual starts to block anything on the Debian side, so no need to hurry (yet ;-) ). |
captured.rs is still broken, see NLnetLabs#42 Signed-off-by: Fabian Grünbichler <[email protected]>
captured.rs is still broken, see NLnetLabs#42 Signed-off-by: Fabian Grünbichler <[email protected]>
I'm currently in the process of updating packaged crates for futures 0.3/tokio 0.2 compatibility in Debian, which also entails updating to bytes 0.5.
Unfortunately bytes 0.4->0.5 does entail some breaking changes, and bcder's Captured/CapturedWriter are affected as well:
call in Captured::extend
I am not sure whether this means that Captured needs to switch over to BytesMut or whether there is a simpler solution. tokio-rs/bytes#368 and tokio-rs/bytes#350 might also be related.
The text was updated successfully, but these errors were encountered: