diff options
| author | bors <bors@rust-lang.org> | 2016-07-12 19:11:02 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-07-12 19:11:02 -0700 |
| commit | 4bbb1c5c9960f221259f6d3b1906999361c9258c (patch) | |
| tree | 9b56c533a9be31bb2fc5f6a4cf4a160ad951274f /src/rustllvm/RustWrapper.cpp | |
| parent | 26fd0117f9a5128d39a30ae36efc731042bd1fec (diff) | |
| parent | cd487db63f7755a603ef6deee9047c3b4251564f (diff) | |
| download | rust-4bbb1c5c9960f221259f6d3b1906999361c9258c.tar.gz rust-4bbb1c5c9960f221259f6d3b1906999361c9258c.zip | |
Auto merge of #34739 - therealbstern:ipv4unspec, r=alexcrichton
Mark Ipv4Addr is_unspecified as stable and provide reference. Per [#27709 (comment)](https://github.com/rust-lang/rust/issues/27709#issuecomment-231280999), no RFC is needed here. IPv4 "unspecified" has been defined in [Stevens], and has been part of the IPv4 stack for quite some time. This property should become stable, since this use of 0.0.0.0 is not going anywhere. [Stevens][_UNIX Network Programming Volume 1, Second Edition_. Stevens, W. Richard. Prentice-Hall, 1998. p. 891] Please let me know if I got the rustdoc wrong or something. I tried to be as terse as possible while still conveying the appropriate information. This also has a slight impact on PR #34694, but that one came first, so this shouldn't block it, IMO.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions