Without such a clarification, people who know and love closures (for instance
programmers with a Haskell background) might fear that types would have to
be declared in closures and that therefore using closures would be much more
unwieldy.

The `Arguments::new_v1_formatted` function was accidentally left out when this
module was stabilized.

This brings it in line with its namesake in `std::io`.

[breaking-change]

Some newcomers might look for a "flatMap" method on Option. Include the
reference so that searching the page would find "and_then".

When matching against strings/slices, we call the comparison function
for strings, which takes two string slices by value. The slices are
passed in memory, and currently we just pass in a pointer to the
original slice. That can cause misoptimizations because we emit a call
to llvm.lifetime.end for all by-value arguments at the end of a
function, which in this case marks the original slice as dead.

So we need to properly create copies of the slices to pass them to the
comparison function.

Fixes rust-lang#22008

The other cases: `concat_idents!`, `log_syntax!`, and `trace_macros!`,
(these macros, with `asm!`, are handled (eagerly) in feature_gate.rs).

Requested by Niko in rust-lang#22200 (and is good to have anyway)

…x::feature_gate

 - We shouldn't be using `check_name` here at all
 - `contains_name(ref_slice(foo), bar)` is redundant, `contains_name` just iterates over its first arg and calls `check_name`
 - match would be better than a bunch of ifs

This redux of CONTRIBUTING.md adds in more information, including
subsuming both compliment-bugreport.md and Note-development-policy
in the wiki.

I only glanced at the broad TOC of Note-development-policy, and did
not use the text as the basis for the re-write. This will then address
the last outstanding part of rust-lang#5831.

Fixes rust-lang#21577.

Fixes rust-lang#22343

The test "signal_reported_right" send a signal `1` to `/bin/sh`, and check
the status code to check if the signal is reported right.

Under OpenBSD, the signal `1` (`SIGHUP`) is catched by `/bin/sh`,
resulting the test failed.

Use the uncatchable signal `9` (`SIGKILL`) for test.

This commit mostly replaces some of the uses of os::args with env::args.

Fixes rust-lang#19321

This is a more introductory document, suitable for Part II.  The arcane details
move to an "Advanced macros" chapter in Part III.

Fix up, add examples, make them all the same.

The first commit adds a short note which I believe will reduce worries in people who work with closures very often and read the Rust book for their first time.

The second commit consists solely of tiny typo fixes. In some cases, I changed "logical" quotations like

    She said, "I like programming".

to

    She said, "I like programming."

because the latter seems to be the prevalent style in the book.

…eklabnik

Some newcomers might look for a "flatMap" method on Option. Include the
reference so that searching the page would find "and_then".

… r=aturon

The `Arguments::new_v1_formatted` function was accidentally left out when this
module was stabilized.

This redux of CONTRIBUTING.md adds in more information, including
subsuming both compliment-bugreport.md and Note-development-policy
in the wiki.

I only glanced at the broad TOC of Note-development-policy, and did
not use the text as the basis for the re-write. This will then address
the last outstanding part of rust-lang#5831.

Fixes rust-lang#21577.

The `Circle::grow` method multiplies the radius by a factor of 10, not 2.

…tsakis

When matching against strings/slices, we call the comparison function
for strings, which takes two string slices by value. The slices are
passed in memory, and currently we just pass in a pointer to the
original slice. That can cause misoptimizations because we emit a call
to llvm.lifetime.end for all by-value arguments at the end of a
function, which in this case marks the original slice as dead.

So we need to properly create copies of the slices to pass them to the
comparison function.

Fixes rust-lang#22008

… r=brson

Requested by Niko in rust-lang#22200 (and is good to have anyway)

cc rust-lang#22240

…akis

This commit mostly replaces some of the uses of os::args with env::args.

This, for obvious reasons is based on top of rust-lang#22400. Do not r+ before that lands.

Fixes rust-lang#19321

... I think? `make check` passes, but I'm not 100% sure that there's a test for that behavior. Thoughts?

I just stumbled on a typo and fixed it.

r? @aturon

…uron

 The test \"signal_reported_right\" send a signal `1` to `/bin/sh`, and check
the status code to check if the signal is reported right.

Under OpenBSD, the signal `1` (`SIGHUP`) is catched by `/bin/sh`,
resulting the test failed.

Use the uncatchable signal `9` (`SIGKILL`) for test.

…nikomatsakis

 fixes rust-lang#22203

r? @nikomatsakis

This breaks code that might be using attributes randomly, so it's technically a

[breaking-change]

 This brings it in line with its namesake in `std::io`.

[breaking-change]

r? @aturon

 Some examples for `std::num::Float`

~~This is WIP for making examples for `f32`. This probably won't pass `make tidy` and I'm not sure which `f32` needs documentation. rust-lang#22025 shows 2 sets of `f32` which seems split between `core` and `std`. I'm not sure which should be documented but I started doing a couple from `std`. Easy to move if that's where they go...~~

~~Gotta build it eventually to actually see if the docs actually appear where I think they will or if I'm just disillusioned.~~

cc @steveklabnik

…-expansion, r=huonw

 Pass features along during expansion

Use the set of passed features to detect uses of feature-gated macros without the corresponding feature enabled.

Fix rust-lang#22234.

----

Also, the framework this add (passing along a reference to the features in the expansion context) is a necessary precursor for landing a properly feature-gated desugaring-based overloaded-`box` and placement-`in` (rust-lang#22181).

----

This is fixing a bug, but since there might be code out there that is unknowingly taking advantage of that bug, I feel obligated to mark this as a:

[breaking-change]

…eklabnik

This is a more introductory document, suitable for Part II. The arcane details move to an "Advanced macros" chapter in Part III.

Conflicts:
	src/doc/trpl/macros.md