If the explicitly given type of a `self` parameter fails to parse correctly,
we need to propagate the error rather than dropping it and causing an ICE.

Fixes rust-lang#62660.

Previously, this callback was never actually called.

poiner -> pointer

Add debug assertions to write_bytes and copy*

Looks like @nitnelave  went MIA in rust-lang#58783, so I am re-submitting their PR, tweaked just a bit. I took care to preserve commit authorship.

Cc rust-lang#53871

Remove never_type feature requirement for exhaustive patterns

I **think** this resolves rust-lang#51221
At least for me, it doesn't ICE anymore and all tests are still passing, so LGTM

…ion, r=QuietMisdreavus

Fix Pin urls in Option documentation

Fixes the following situation:

![Screenshot from 2019-07-08 13-24-59](https://user-images.githubusercontent.com/3050060/60806822-55dfdc00-a184-11e9-9ee3-279e82fc92bd.png)

r? @QuietMisdreavus

…eallocInPlace, r=QuietMisdreavus

Add missing links for CannotReallocInPlace type

r? @QuietMisdreavus

Less unsafe in the array example of MaybeUninit docs

I believe this is an acceptable way to initialize elements of `[MaybeUninit<T>; _]` arrays. Miri agrees. Conceptually, we are working at the array level, above the `MaybeUninit`, and as we are replacing it wholesale, this should pose no problem to soundness. And the code is easier to read.

r? @RalfJung

Make VaListImpl<'f> invariant over the 'f lifetime

After doing some research on variance and going back to look at `VaList` and `VaListImpl`, I realized that `VaList<'a, 'f>` is invariant over the `'f` lifetime (and covariant over `'a`), but `VaListImpl<'f>` isn't invariant but probably should be. This patch makes `VaListImpl<'f>` invariant over `'f`.

r? @eddyb
cc @dlrobertson

Tweak wording in feature gate errors

add spaces in front of trait requirements in libcore/cell.rs

Adds spaces before trait requirements in `libcore/cell.rs`.

Fix rust-lang#62660

If the explicitly given type of a `self` parameter fails to parse correctly, we need to propagate the error rather than dropping it and causing an ICE.

Fixes rust-lang#62660.

miri validation: better error messages for dangling references

Cc @oli-obk

…-consumer, r=matthewjasper

Actually call `visit_block_entry` in `DataflowResultsConsumer`

This fixes a trivial bug in `DataflowResultsConsumer`: `visit_block_entry` is never called when visiting dataflow results.

A previous version of rust-lang#62547 used this API and included this fix, but it has since switched to `DataflowResultsCursor` making this commit irrelevant.

…tebank

Add info about undefined behavior to as_ref suggestions

Fixes rust-lang#61786. A very small fix, but suggestions on wording/content are welcomed.

Fix typo in RawWaker::new documentation

poiner -> pointer

…crichton

SGX target: don't pretend to be GNU/Linux to LLVM

See rust-lang#62592 & rust-lang/compiler-builtins#303

r? @alexcrichton