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

Support futures 0.3 streams for IPC channels #227

Merged
merged 3 commits into from May 6, 2019

Conversation

@asajeffrey
Copy link
Member

asajeffrey commented Mar 4, 2019

Fixes #219

…em to be used in async settings
@asajeffrey
Copy link
Member Author

asajeffrey commented Mar 4, 2019

This is a breaking change to the API, so needs a bump to 0.12.

The implementation uses OpaqueIpcReceiver, which isn't supported by IpcBytesReceiver, so I couldn't see how to implement Stream for it.

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.

@asajeffrey
Copy link
Member Author

asajeffrey commented Mar 4, 2019

r? @antrik

@asajeffrey
Copy link
Member Author

asajeffrey commented Mar 11, 2019

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.

@dlrobertson

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.

@asajeffrey

asajeffrey Apr 1, 2019

Author Member

It's AsyncRouter vs async::Router which I don't have strong opinions about.

@asajeffrey
Copy link
Member Author

asajeffrey commented May 6, 2019

Review ping @antrik or @dlrobertson?

Copy link
Collaborator

dlrobertson left a comment

Looks good to me, but I'm not as familiar with futures or the ROUTER.

@asajeffrey
Copy link
Member Author

asajeffrey commented May 6, 2019

@bors-servo r=dlrobertson

@bors-servo
Copy link
Contributor

bors-servo commented May 6, 2019

📌 Commit 2592931 has been approved by dlrobertson

@highfive highfive assigned dlrobertson and unassigned jdm May 6, 2019
@bors-servo
Copy link
Contributor

bors-servo commented May 6, 2019

Testing commit 2592931 with merge f9de331...

bors-servo added a commit that referenced this pull request May 6, 2019
Support futures 0.3 streams for IPC channels

Fixes #219
@bors-servo
Copy link
Contributor

bors-servo commented May 6, 2019

💔 Test failed - status-appveyor

@asajeffrey
Copy link
Member Author

asajeffrey commented May 6, 2019

Argh, async is a keyword these days.

81 | pub mod async;
   |         ^^^^^ expected identifier, found reserved keyword
help: you can escape reserved keywords to use them as identifiers
   |
81 | pub mod r#async;
   |         ^^^^^^^
@asajeffrey
Copy link
Member Author

asajeffrey commented May 6, 2019

@bors-servo r=dlrobertson

@bors-servo
Copy link
Contributor

bors-servo commented May 6, 2019

📌 Commit 5cf299d has been approved by dlrobertson

@bors-servo
Copy link
Contributor

bors-servo commented May 6, 2019

Testing commit 5cf299d with merge 7cc64eb...

bors-servo added a commit that referenced this pull request May 6, 2019
Support futures 0.3 streams for IPC channels

Fixes #219
@bors-servo
Copy link
Contributor

bors-servo commented May 6, 2019

☀️ Test successful - checks-travis, status-appveyor
Approved by: dlrobertson
Pushing 7cc64eb to master...

@bors-servo bors-servo merged commit 5cf299d into servo:master May 6, 2019
3 checks passed
3 checks passed
Travis CI - Pull Request Build Passed
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
homu Test successful
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

5 participants
You can’t perform that action at this time.