Helps users to understand capacity related values, which may surpise on
Windows.

Also is a step towards clarifying understanding of `OsStr`'s len() return
value.

The previous one didn't actually use the Display&Debug bounds in any way, so I think this one is a bit more meaningful.

This rule was introduced by rust-lang#45401.

Currently libproc_macro does not use `DotEq` token.
rust-lang#49545 changed libproc_macro
to not generate `DotEq` token.

[std] Osstr len clarity

… r=Centril

Stabilize self_in_typedefs feature

[**Tracking Issue**](rust-lang#49303)

r? @Centril

…nSapin

Stabilize dbg!(...)

Per FCP in rust-lang#54306 (which is ~1 day from completion).

r? @SimonSapin

The PR is fairly isolated so a rollup should probably work.

…olnay

Move VecDeque::resize_with out of the impl<T:Clone> block

I put this in the wrong `impl` block in rust-lang#56016, so fixing.

Tracking issue for the unstable method: rust-lang#41758 (comment)

…e, r=Centril

Improve the unstable book example for #[marker] trait

The previous one didn't actually use the Display&Debug bounds in any way, so I think this one is a bit more meaningful.

Update tracking issue for `extern_crate_self`

…dreavus

Remove unneeded body class selector

r? @QuietMisdreavus

Fix failing tidy (line endings on Windows)

Updates to `rustc-guide` and `edition-guide` including rust-lang/rustc-dev-guide#246 and rust-lang/edition-guide#122.

Remove some uses of try!

Update issue number of `shrink_to` methods to point the tracking issue

Tracking issue: rust-lang#56431

…ibility, r=petrochenkov

Add description about `crate` for parse_visibility's comment

This rule was introduced by rust-lang#45401.

…ichton

make the C part of compiler-builtins opt-out

I'd like to be able to use Xargo to build a libstd without having a full C toolchain for the target.  This is a start (but the fact that libstd is a dylib is still a problem).

However, compiler_builtin already has somewhat similar logic to not require a C compiler for wasm:

https://github.com/rust-lang-nursery/compiler-builtins/blob/fe74674f6e4be76d47b66f67d529ebf4186f4eb1/build.rs#L36-L41

(WTF GitHub, why doesn't this show an embedded code preview??)

I wonder if there is a way to not have two separate mechanisms? Like, move the above wasm logic to some place that controls the libstd feature, or so? Or is it okay to have these two mechanisms co-exist?

Cc @alexcrichton

…, r=petrochenkov

Remove not used `DotEq` token

Currently libproc_macro does not use `DotEq` token.
rust-lang#49545 changed libproc_macro
to not generate `DotEq` token.