-
Notifications
You must be signed in to change notification settings - Fork 961
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
core/transport: Remove various Sync
bounds
#2667
core/transport: Remove various Sync
bounds
#2667
Conversation
With `Transport` becoming non-Clone and having `&mut` self receivers, the `Sync` requirement no longer makes any sense and we can thus remove it.
Sync
boundsSync
bounds
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.
Nice! I actually stumbled over that recently because it was that reason that you could not call boxed
directly on the tcp transport. So this will also make #2652 (comment) easier.
Was about to merge this but will hold back until 0.45.0 is out. |
With PR libp2p#2667 the `Sync` trait bound for transport::Boxed is removed. If a tcp transport should be polled as a stream we can now do this via `TcpTransport::new(..)::boxed` and do not need a separate impl of `Stream` for it.
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.
Thanks!
I am in favor of including this in v0.45.0
.
Okay, up to you! |
Description
With
Transport
becoming non-Clone and having&mut
self receivers,the
Sync
requirement no longer makes any sense and we can thusremove it.
Links to any relevant issues
StreamMuxer
trait #2648.Open Questions
Change checklist