Skip to content

std: Deprecate extra TcpStream/UdpSocket methods #27368

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

Merged
merged 1 commit into from
Jul 29, 2015

Conversation

alexcrichton
Copy link
Member

These methods are all covered by RFC 1158 and are currently all available on
stable Rust via the net2 crate on crates.io. This commit does not
touch the timeout related functions as they're still waiting on Duration which
is unstable anyway, so punting in favor of the net2 crate wouldn't buy much.

These methods are all covered by [RFC 1158] and are currently all available on
stable Rust via the [`net2` crate][net2] on crates.io. This commit does not
touch the timeout related functions as they're still waiting on `Duration` which
is unstable anyway, so punting in favor of the `net2` crate wouldn't buy much.

[RFC 1158]: rust-lang/rfcs#1158
[net2]: http://crates.io/crates/net2

Specifically, this commit deprecates:

* TcpStream::set_nodelay
* TcpStream::set_keepalive
* UdpSocket::set_broadcast
* UdpSocket::set_multicast_loop
* UdpSocket::join_multicast
* UdpSocket::set_multicast_time_to_live
* UdpSocket::set_time_to_live
@alexcrichton alexcrichton added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label Jul 28, 2015
@alexcrichton
Copy link
Member Author

r? @aturon

@rust-highfive rust-highfive assigned aturon and unassigned nikomatsakis Jul 28, 2015
@rust-highfive
Copy link
Contributor

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

@alexcrichton alexcrichton force-pushed the deprecate-net-methods branch from 7196b3e to 798ce50 Compare July 28, 2015 23:12
@aturon
Copy link
Member

aturon commented Jul 29, 2015

I'm a bit puzzled by the rationale here: why deprecate these when the plan is, ultimately, to stabilize them?

@alexcrichton
Copy link
Member Author

Almost all of these functions will have their signatures changed anyway, and I figured it'd be good to encourage any current users to try out the net2 crate (which works on stable Rust) instead of the nightly-only features here.

@aturon
Copy link
Member

aturon commented Jul 29, 2015

Ah OK, I had forgotten that there were signature changes as well. In that case:

@bors: r+

@bors
Copy link
Collaborator

bors commented Jul 29, 2015

📌 Commit 798ce50 has been approved by aturon

@bors
Copy link
Collaborator

bors commented Jul 29, 2015

⌛ Testing commit 798ce50 with merge 823f4fc...

bors added a commit that referenced this pull request Jul 29, 2015
These methods are all covered by [RFC 1158] and are currently all available on
stable Rust via the [`net2` crate][net2] on crates.io. This commit does not
touch the timeout related functions as they're still waiting on `Duration` which
is unstable anyway, so punting in favor of the `net2` crate wouldn't buy much.

[RFC 1158]: rust-lang/rfcs#1158
[net2]: http://crates.io/crates/net2
@bors bors merged commit 798ce50 into rust-lang:master Jul 29, 2015
@alexcrichton alexcrichton deleted the deprecate-net-methods branch August 17, 2015 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants