According to @dotdash it enables more aggressive optimizations from LLVM

Fixes rust-lang#22233

It is not totally clear if we should just use whitespace, or if the full
unicode word-breaking algorithm is more correct. If there is demand we
can reconsider this decision (and consider the precise algorithm to use
in detail).

cc rust-lang#15628.

In `std::f32` and `std::f64`:

- `MIN_VALUE` → `MIN`
- `MAX_VALUE` → `MAX`
- `MIN_POS_VALUE` → `MIN_POSITIVE`

This matches the corresponding integer constants.

[breaking-change]

Also add address of IRC server. Addresses rust-lang#22249.

This partially resolves rust-lang#22243.

This resolves rust-lang#22243, at least for one-letter variable names.

Fixes rust-lang#16645

Remove incorrect claim, add example, reformat and re-word.

Fixes rust-lang#22266

Fixes rust-lang#22136

Fixes rust-lang#22035.

Fixes rust-lang#22064.

Rollup merge (373cbab) of PR rust-lang#20723
accidentally reverted a portion of commit
8327bcc which shifted
`slicing_syntax` from Active to Accepted.

We use them in some places, but never actually talk about the syntax.

Added a second note about keeping the reference.md list up-to-date to
the bottom of the list, since not everyone (including me) reads the
big comment at the top of it.  :)

Ensured that the feature gate list in reference.md is kept in
alphabetical order.

if found on the `main()` function. This lets you write tests that live
in `compile-fail` but are expected to compile successfully. This is
handy when you have many small variations on a theme that you want to
keep together, and you are just testing the type checker, not the
runtime semantics.

This isn't something we want to guarantee.

Fixes rust-lang#9980

Fixes rust-lang#22047

Range<u64> and Range<i64> may be longer than usize::MAX on 32-bit
platforms, and thus they cannot fulfill the protocol for
ExactSizeIterator. We don't want a nonobvious platform dependency in
basic iterator traits, so the trait impl is removed.

The logic of this change assumes that usize is at least 32-bit.

This is technically a breaking change; note that Range<usize> and
Range<isize> are always ExactSizeIterators.

[breaking-change]

rustc --version says

```
rustc 1.0.0-dev (d0e82a6 2015-02-05) (built 2015-02-11)
```

closes rust-lang#21909

Fixes rust-lang#14849

Fixes rust-lang#19278

Fixes rust-lang#20948

This overhauls the very meager docs that currently exist to clarify
various understandable confusions that I've noticed, e.g. people look in
`std::raw` for the "real" types of slices like `&[T]`, or think that
`Slice<T>` refers to `[T]` (fixes rust-lang#22214).

This patch takes the liberty of offering some "style" guidance around
`raw::Slice`, since there's more restricted ways to duplicate all
functionality connected to it: `std::slice::from_raw_parts{,_mut}` for
construction and `.as_{,mut_}ptr` & `.len` for deconstruction.

It also deprecates the `std::raw::Closure` type which is now useless for
non-type-erased closures, and replaced by `TraitObject` for `&Fn`, `&mut
FnMut` etc, so I guess it should be called a:

[breaking-change]

The default implementation of .repr() will call conveniently call
transmute_copy which should be appropriate for all implementors, but is
memory unsafe if used wrong.

Fixes rust-lang#22260

You need to use `unsafe impl` to implement the Repr trait now.

[breaking-change]

Closes rust-lang#22306.

(fixes rust-lang#22317)

crates-and-modules - replace ")"
more string - improve readability of grapheme

Fixes rust-lang#16645

Fixing this in any deeper way will require an RFC, so let's just document the current behavior.

rustc --version says

```
rustc 1.0.0-dev (d0e82a6 2015-02-05 14:38:56 -0800) (built 2015-02-11)
```

This overhauls the very meager docs that currently exist to clarify
various understandable confusions that I've noticed, e.g. people look in
`std::raw` for the "real" types of slices like `&[T]`, or think that
`Slice<T>` refers to `[T]` (fixes rust-lang#22214).

This patch takes the liberty of offering some "style" guidance around
`raw::Slice`, since there's more restricted ways to duplicate all
functionality connected to it: `std::slice::from_raw_parts{,_mut}` for
construction and `.as_{,mut_}ptr` & `.len` for deconstruction.

It also deprecates the `std::raw::Closure` type which is now useless for
non-type-erased closures, and replaced by `TraitObject` for `&Fn`, `&mut
FnMut` etc, so I guess it should be called a:

[breaking-change]

Fix rust-lang#20109.

According to @dotdash it enables more aggressive optimizations from LLVM

…hton

Fixes rust-lang#22233 

r? @alexcrichton

It is not totally clear if we should just use whitespace, or if the full
unicode word-breaking algorithm is more correct. If there is demand we
can reconsider this decision (and consider the precise algorithm to use
in detail).

cc rust-lang#15628.

In `std::f32` and `std::f64`:

- `MIN_VALUE` → `MIN`
- `MAX_VALUE` → `MAX`
- `MIN_POS_VALUE` → `MIN_POSITIVE`

This matches the corresponding integer constants.

[breaking-change]

…xcrichton

`Unsafe` was renamed to `UnsafeCell` a while ago, but the corresponding lang item kept the old name. This patch fixes the inconsistency.

r? @eddyb

…akis

Removes the link to the rust-dev mailing list in the bug report submission page and also adds the address of the IRC server (`irc.mozilla.org`). Addresses rust-lang#22249.

While having a look at the Rust book I found this tiny error. In my opinion this if should be all lowercase, because it follows a colon, but I am no native speaker, so I am probably wrong. Also it is a very tiny change, so feel free to include it in any bigger documentation patch.

…tsakis

Remove incorrect claim, add example, reformat and re-word.

Fixes rust-lang#22266

Fixes rust-lang#22136

Fixes rust-lang#22035. (mostly by making it irrelevant)

Fixes rust-lang#22064.

…cepted, r=nikomatsakis

Re-tag `slicing_syntax` as `Accepted`.

Rollup merge (373cbab) of PR rust-lang#20723
accidentally reverted a portion of commit
8327bcc which shifted
`slicing_syntax` from Active to Accepted.

We use them in some places, but never actually talk about the syntax.

This resolves rust-lang#22243 for the single-letter variables that I could grep. Some occurences could not be replaced.

…ate-list, r=steveklabnik

Added all active features to the list in reference.md.

Added a second note about keeping the reference.md list up-to-date to the bottom of the list, since not everyone (including me) reads the big comment at the top of it.  :)

Ensured that the feature gate list in reference.md is kept in alphabetical order.

…sakis

Add `#[rustc_error]` annotation, which causes trans to signal an error
if found on the `main()` function. This lets you write tests that live
in `compile-fail` but are expected to compile successfully. This is
handy when you have many small variations on a theme that you want to
keep together, and you are just testing the type checker, not the
runtime semantics.

r? @pnkfelix

…omatsakis

This isn't something we want to guarantee.

r? @nikomatsakis

…omatsakis

Fixes rust-lang#9980

…=alexcrichton

Fixes rust-lang#22047

`Range<u64>` and `Range<i64>` may be longer than usize::MAX on 32-bit
platforms, and thus they cannot fulfill the protocol for
ExactSizeIterator. We don't want a nonobvious platform dependency in
basic iterator traits, so the trait impl is removed.

The logic of this change assumes that usize is at least 32-bit.

This is technically a breaking change; note that `Range<usize>` and
`Range<isize>` are always ExactSizeIterators.

[breaking-change]

closes rust-lang#21909

Fixes rust-lang#20948

Fixes rust-lang#14849

Fixes rust-lang#19278

(fixes rust-lang#22317)

rollupable

on crates and modules - replace ")"
on more strings - improve readability of grapheme

Rename `libstd/failure.rs` to `libstd/panicking.rs` and `on_fail` to `on_panic`. Closes rust-lang#22306.