`socket_addr` was renamed to `local_addr` in 1.0beta.

See: f798674b

r? @steveklabnik

`socket_addr` was renamed to `local_addr` in 1.0beta.

See: f798674b

This was to support rustpkg but is unused now.

- Successful merges: #30013, #30038, #30040
- Failed merges: #30030

Closes #30031.

At this point of the book, reader have likely use `cargo new --bin`,
likely 2 times, once if they are lazy. This remind them of the `cargo`
syntax.

I was myself unsure whether it was `cargo create`, `cargo new`, and
whether it would initialize in current working directory or needed a
target.

--

Otherwise thanks, I've been writing rust for a few hours, and likes it so far.

Part of https://github.com/rust-lang/rust/issues/29333

Fixes #22425

Also fixes #30007, since it's just a change from `true` to `false`.

See https://github.com/rust-lang/rfcs/pull/1246 for discussion.

Typical algebra currently doesn't work on the types in std::time currently (see
[this comment][comment]), so tweak the tests to account for this property.

[comment]: https://github.com/rust-lang/rust/issues/29866#issuecomment-159093809

Closes #29970

Closes #30031.

Closes #25810.
Closes #29276.

r? @alexcrichton

At this point of the book, reader have likely use `cargo new --bin`,
likely 2 times, once if they are lazy. This remind them of the `cargo`
syntax.

I was myself unsure whether it was `cargo create`, `cargo new`, and
whether it would initialize in current working directory or needed a
target.

Trait references are always invariant, so all uses of subtyping between
them are equivalent to using equality.

Moreover, the overlap check was previously performed twice per impl
pair, once in each direction. It is now performed only once, and
internally uses the equality check.

On glium, a crate that spends some time in coherence, this change sped
up coherence checking by a few percent (not very significant).

r? @nikomatsakis

This was to support rustpkg but is unused now.

Part of https://github.com/rust-lang/rust/issues/29333

- Successful merges: #29397, #29933, #30004, #30019, #30020, #30023
- Failed merges:

`unit` was in code formatting, which is wrong, since it's not actual code. The correct code is `()`.

looks like a case of mixed tabs and spaces

Good candidate for a rollup, this one.

It was introduced with the change that made copy opt-in. The
implementation gives a warning, because the struct contains a raw
pointer.

Previously the file was not regenrated upon modification of `src/rustllvm` or others.

Now it will be rebuilt if `src/llvm` or `src/rustllvm` is touched.

Also added *.rs rule to 'clean' rule so that it is removed upon 'make
clean'.

Fixes #28614.

Fixes #29861 - it was a bug I accidentally introduced in #26275.

r? @nikomatsakis

The `log` crate on crates.io already knows `TRACE`, but the internal liblog doesn't, which causes it to spew errors when a `TRACE` level is defined. I made `TRACE` behave like `DEBUG`.

Fixes #1889

looks like a case of mixed tabs and spaces

It seems that OS X El Capitan does not pass DYLD_* environment variables to child processes anymore.  See this link: https://forums.developer.apple.com/thread/9233

The causes a test in `src/libstd/process.rs' to fail when those environment variables are not found in the child process.  This PR skips those variables similar to how the Windows envars that start with `=` are skipped.

r? @Manishearth

Typical algebra currently doesn't work on the types in std::time currently (see
[this comment][comment]), so tweak the tests to account for this property.

[comment]: https://github.com/rust-lang/rust/issues/29866#issuecomment-159093809

Closes #29970