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

Upgrade websocket transport to soketto 0.3.0. #1266

Merged
merged 4 commits into from
Oct 8, 2019

Conversation

twittner
Copy link
Contributor

@twittner twittner commented Oct 1, 2019

Currently pointing to twittner's repo until the corresponding PR is merged. Also forces futures-preview to alpha.18 dues to breaking changes w.r.t. AsyncRead's initializer API.

Currently pointing to twittner's repo until the corresponding PR is
merged. Also forces futures-preview to alpha.18 dues to breaking changes
w.r.t. AsyncRead's initializer API.
async fn dial_once
( self
, address: Multiaddr
) -> Result<Either<String, BytesConnection<T::Output>>, Error<T::Error>>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That code style looks like abstract art.

Copy link
Member

@tomaka tomaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, I'm just undecided whether I'm opposed or not to this weird style.
The point of code style is for it to be common amongst all people that touch a certain code base, and you're the one and only person in the world I've seen that does this.

@tomaka
Copy link
Member

tomaka commented Oct 2, 2019

(let's merge paritytech/soketto#3 first and update the Cargo.toml)

@twittner twittner merged commit 9921a33 into libp2p:stable-futures Oct 8, 2019
@twittner twittner deleted the new-websocket branch October 8, 2019 09:50
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.

3 participants