Explain why Rust does not implement traits for large arrays.

Explain why most methods are implemented on slices rather than arrays.

Fixes rust-lang#35642.

The spacing seems inconsistent with existing style conventions.

Some people cite this list as "zomg Rust has so many keywords," so make
it clear that these aren't all used by the language today.

Part of rust-lang#29330

I'm only making this change in one place so that people can express
their preferences for this stylistic change. If/when this change is
approved I'll go ahead and translate the rest of the `std::ops`
examples.

Display all the remaining items of the iterator, similar to the `Debug`
implementation for `core::slice::Iter`:

https://github.com/rust-lang/rust/blob/f0bab98695f0a4877daabad9a5b0ba3e66121392/src/libcore/slice.rs#L930-L937

Using the `as_slice` method that was added in:

rust-lang#35447

…=Manishearth

A disclaimer about keywords.

Some people cite this list as "zomg Rust has so many keywords," so make
it clear that these aren't all used by the language today.

…andturner

Update compiler error 0030 to use new error format.

Part of rust-lang#35233,
Addresses rust-lang#35204

r? @jonathandturner

…=steveklabnik

Clarify type declaration language in Associated Types docs

A small fix for the Associated Types docs

r? @steveklabnik

…-representaton, r=steveklabnik

Add note to docs for &str that example is to demo internals only

r? @steveklabnik

This adds a note below the &str representation example explaining that the example provided should not be used under normal circumstances..

Would it make sense to point people in the direction of the method(s) they should use instead?  I left it out in the interest of not complicating the documentation, but, there's definitely an argument to be made for adding a bit of guidance in there.

…tification, r=steveklabnik

provide additional justification for array interface design

Explain why Rust does not implement traits for large arrays.

Explain why most methods are implemented on slices rather than arrays.

Note: I'm dipping my toes in the water with a tiny PR. Especially looking for feedback on wording and style. Points of concern: appropriate level of top-level explanation; foreshadowing (is it appropriate to imply that we expect Rust's type system to eventually support size-generic arrays?); using `Foo` and `Bar` as type variables instead of e.g. `T` and `S`.

@peschkaj

…=nikomatsakis

run rustfmt on libsyntax_ext folder

…schkaj

Add doc example for `std::ffi::CString::from_vec_unchecked`.

None

Update E0207 label to report parameter type

Fixes rust-lang#35642.

r? @jonathandturner (Is this okay? I tagged you since it's a simple error fix similar to the other update ones.)

Improve `No stdlib` and related Documentation

This renames all lang item function names to the ones used in `libstd` and `libpanic_unwind`. It also explains the `eh_unwind_resume` lang item in the `libcore` documentation, where it was missing. A third function is also needed on certain compilation targets, so this was also added to the `No stdlib` documentation.

Update error E0365 to new format

Fixes rust-lang#35633 as part of rust-lang#35233.

r? @jonathandturner

Update E0392 to new error format

Fixes rust-lang#35631. Part of rust-lang#35233
r? @jonathandturner or @GuillaumeGomez

Update E0322 to new format

Fixes rust-lang#35323. Part of rust-lang#35233.
r? @GuillaumeGomez

Fix spacing in code of closures.md

The spacing seems inconsistent with existing style conventions.

update E0375 to new format

fixes rust-lang#35635 as part of rust-lang#35233.

r? @jonathandturner

…ed, r=steveklabnik

expound on limitations of Rust's trait-based operator overloading

Part of rust-lang#29330

…tln, r=GuillaumeGomez

accumulate into vector and assert, instead of printing

I'm only making this change in one place so that people can express
their preferences for this stylistic change. If/when this change is
approved I'll go ahead and translate the rest of the `std::ops`
examples.

…xcrichton

Implement `Debug` for `std::vec::IntoIter`.

Display all the remaining items of the iterator, similar to the `Debug`
implementation for `core::slice::Iter`:

https://github.com/rust-lang/rust/blob/f0bab98695f0a4877daabad9a5b0ba3e66121392/src/libcore/slice.rs#L930-L937

Using the `as_slice` method that was added in:

rust-lang#35447

…sakis

RUST_NEW_ERROR_FORMAT is no more

So stop setting the environment variable.

Use UI test to test spans, instead of forced line break

There must be lots more, but these are what I could easily find.

…andturner

Updated E0394 & E0422 to new format

Fixes rust-lang#35692 and rust-lang#35700, as part of rust-lang#35233.

r? @jonathandturner

Bump version to 1.13

update E0409 to new error format

fixes rust-lang#35699 as part of rust-lang#35233.

r? @jonathandturner

Update E0005 to use a label

Fixes rust-lang#35192 as Part of rust-lang#35233

r? @jonathandturner