Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport futures 0.3 streams for IPC channels #227
Conversation
…em to be used in async settings
|
This is a breaking change to the API, so needs a bump to The implementation uses Since futures 0.3 is still only on nightly, this PR means that async is now only on nightly. We could try to maintain both, but that seems difficult. |
|
r? @antrik |
|
Ping? @antrik |
| impl<T> Unpin for IpcStream<T> {} | ||
|
|
||
| // A router which routes from an IPC channel to a stream. | ||
| struct Router { |
This comment has been minimized.
This comment has been minimized.
dlrobertson
Mar 31, 2019
Collaborator
Router and ROUTER are used in router.rs. Would it make sense to rename these to AsyncRouter and ASYNC_ROUTER?
This comment has been minimized.
This comment has been minimized.
asajeffrey
Apr 1, 2019
Author
Member
It's AsyncRouter vs async::Router which I don't have strong opinions about.
|
Review ping @antrik or @dlrobertson? |
|
Looks good to me, but I'm not as familiar with futures or the |
|
@bors-servo r=dlrobertson |
|
|
|
|
|
Argh,
|
|
@bors-servo r=dlrobertson |
|
|
|
|
asajeffrey commentedMar 4, 2019
Fixes #219