Link to http://rustbyexample.com/

Reviewed-by: steveklabnik

Make rustdoc use the `[_; N]` syntax instead of `[_, ..N]`

Reviewed-by: sfackler

Better iOS support

Reviewed-by: alexcrichton

Changed alignment according to official Apple docs

Now it is possible to run tests on a jailbroken device

- target_word_size -> target_pointer_width
- added armv7 and armv7s targets
- enabled building binaries so tests could be run on a jailbroken device

Fixes #19907

Because we are warning about unstable APIs and there are many
of these yet, this creates a high likelyhood doc tests will
fail.

This doesn't seem right as a blanket policy to me anyway, though
certainly we want it in std. Probably more appropriate to add
a rustdoc option.

Fixes #19907

Because we are warning about unstable APIs and there are many
of these yet, this creates a high likelyhood doc tests will
fail.

This doesn't seem right as a blanket policy to me anyway, though
certainly we want it in std. Probably more appropriate to add
a rustdoc option.

mk: Update prerelase versioning to conform to semver

Reviewed-by: alexcrichton

Fix assertion in Mutex::destroy() on DragonFly (#20698)

Reviewed-by: alexcrichton

bench: fix a few compiler warnings

Reviewed-by: alexcrichton

doc: Fix unresolved import in Bitv example

Reviewed-by: alexcrichton

Spelling fix compatibel -> compatible

Reviewed-by: Gankro

On DragonFly pthread_{mutex,rwlock,condvar}_destroy() returns EINVAL
when called on a pthread_{mutex,rwlock,condvar}_t that was just
initialized via PTHREAD_{MUTEX,RWLOCK,CONDVAR}_INITIALIZER and not used
in the meantime or initialized via pthread_{mutex,rwlock,condvar}_init().
Change the code to treat a return value of EINVAL on DragonFly as success.

Conflicts:
	src/test/compile-fail/borrowck-move-out-of-overloaded-auto-deref.rs
	src/test/compile-fail/issue-2590.rs
	src/test/compile-fail/lint-stability.rs
	src/test/compile-fail/slice-mut-2.rs
	src/test/compile-fail/std-uncopyable-atomics.rs

Issue #20232. Fun.

r? @EddyB you prob know this system best

Most of the file lost one level of indentation in a recent rollup. Most
likely an accident during merge conflict resolution.

[breaking-change] code using this feature will break.

This gets rid of the 'experimental' level, removes the non-staged_api
case (i.e. stability levels for out-of-tree crates), and lets the
staged_api attributes use 'unstable' and 'deprecated' lints.

This makes the transition period to the full feature staging design
a bit nicer.

An updated version of https://github.com/rust-lang/rust/pull/19461

This version vendors aturon/rust-book@731f7bf and builds it when building the docs. This is almost great, except my `make`-foo is poor, so I have my own personal paths in `mk/docs.mk`. How should I best get around that?

/cc @brson

This pulls all of our long-form documentation into a single document,
nicknamed "the book" and formally titled "The Rust Programming
Language."

A few things motivated this change:

* People knew of The Guide, but not the individual Guides. This merges
  them together, helping discoverability.
* You can get all of Rust's longform documentation in one place, which
  is nice.
* We now have rustbook in-tree, which can generate this kind of
  documentation. While its style is basic, the general idea is much
  better: a table of contents on the left-hand side.
* Rather than a almost 10,000-line guide.md, there are now smaller files
  per section.