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

Fix: tokio_net::tcp::incoming::Incoming type not exported #1602

Merged
merged 1 commit into from
Oct 2, 2019

Conversation

vojtechkral
Copy link
Contributor

@vojtechkral vojtechkral commented Sep 25, 2019

Motivation

With tokio 0.2.0-alpha.5, We can't use the Incoming stream type in our types, because it's not exported. For the same reason, it can't be viewed in the documentation (also dead link here).

Solution

pub use the Incoming in the tcp module.

Not sure about tests. Does it make sense to make a test for this?

@vojtechkral vojtechkral changed the title Fix: Incoming type not exported Fix: tokio_net::tcp::incoming::Incoming type not exported Sep 25, 2019
@vojtechkral
Copy link
Contributor Author

vojtechkral commented Sep 25, 2019

Hang on, this is not right, there's still export missing in net.rs ... Fixed.

@vojtechkral
Copy link
Contributor Author

ping @carllerche
Really sorry to bother, but this is hindering our transition from 0.1 to 0.2

@carllerche
Copy link
Member

I'm hoping to put together a compat crate that helps bridge the gap between 0.1 and 0.2. This crate could provide Incoming.

I want to avoid providing it in the main crate until we know we want to commit to it. I will setup some tracking issues for -compat work.

@carllerche
Copy link
Member

Actually, lets merge this for now.

@carllerche
Copy link
Member

We can follow up in #1549

@carllerche carllerche merged commit aefaef3 into tokio-rs:master Oct 2, 2019
janbraiins pushed a commit to braiins/braiins-open that referenced this pull request Apr 19, 2021
- Upgrade Tokio from 0.1.19 to 0.2.0-alpha5
- Use toolchain nightly-2019-08-21
- Using our fork of Tokio because of tokio-rs/tokio#1602
- Using pin-project to deal with pinning of struct fields
- Connection::send() renamed to send_msg() to avoid conflict with StreamExt::send()
- The socket split hack is still needed even in Tokio 0.2, refactored, now in split.rs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants