…cutable from 'Converting to Cargo'.

Fixes: rust-lang#32214

There was no span available in the cast function, but we need to infer the `x` in `x as char` to `u8`.
The spans are now removed from all functions using `infer` and instead added in `eval_const_expr_partial`

The implementation mirrors the one for "constant defined here" annotation
used for constant patterns in the irrefutable-pattern case.

Fixes: rust-lang#23716

Was causing severe performance problems in WebRender.

This will go wrong when the constants partially result from macro expansion.
Instead, use the expressions and pretty-print them as Rust code.

Fixes: rust-lang#33302

Especially in cases like the one in the test file, this can blow
up the docs big time if string constants in the code contain HTML.

But also other constants can contain special chars (e.g. `&` as an
operator in constant expressions).

…=steveklabnik

Fix std::fmt format spec: named args are allowed with "$" syntax

Add detailed error explanation for E0501

r? @GuillaumeGomez

Bring on the nits!

doc/book/getting-started.md: Spelling correction and revised wording.

The word 'Internet' was spelt with both an uppercase and a lowercase 'I'. The correct spelling seems to be a matter of some debate these days, however the first occurrence in the file has an uppercase 'I', so I've changed the second occurrence to suit for consistency.

Under the section titled 'Converting to Cargo', there's mention of creating a new executable. This, however, is not part of the process described. I've revised the wording to reflect as much.

Small changes, but I hope they are of benefit! :-)

r? @steveklabnik

fix various const eval errors

These were found after const_evaluating arbitrary expressions and linting if the const evaluator failed

fixes rust-lang#33275 (int -> float casts for negative ints)
fixes rust-lang#33291 (int -> char casts (new! wasn't allowed in constants until this PR))

r? @eddyb

cc @bluss @japaric

resolve: print location of static for "static in pattern" error

The implementation mirrors the one for "constant defined here" annotation used for constant patterns in the irrefutable-pattern case.

Fixes: rust-lang#23716

parser: change warning into an error on `T<A=B, C>`

part of rust-lang#32214

This seems to be the obvious fix, and the error message is consistent with all the other parser errors ("expected x, found y").

libcore: Inline `mem::forget()`.

Was causing severe performance problems in WebRender.

r? @brson

rustdoc: fix inserting source code spans for constant values

This will go wrong when the constants partially result from macro expansion.
Instead, use the expressions and pretty-print them as Rust code.

Fixes: rust-lang#33302

rustdoc: HTML-escape Rust code (from constants)

Especially in cases like the one in the test file, this can blow up the rendering big time if string constants in the code contain HTML.

But also other constants can contain special chars (e.g. `&` as an operator in constant expressions).