vim: disable nested comment

Since comment nesting does not work from 0.4.
vim: add rustCommentDoc
vim: fix comment highlighting bug

Previous commit had a bug that a line which ends with "//" or "/*"
is not correctly highlighted.
Update tutorial: 1-tuples now exist
Update manual for single-element tuples
Update manual for single-element tuple types
Fixed typo

Change wrong field name in "Trait Inheritance" section.
libcore: from_str_common: correctly signal failure on repeating base 2^n numbers.

A number like 0b1_1111_1111 == 511 would be parsed to Some(255u8) rather than None
by from_str_common, since 255 * 2 + 1 == 255 (mod 256) so the overflow wasn't detected.

Only applied to conversions where the radix was a power of 2, and where all digits
repeated.

Closes #5770.
libcore: from_str_common: provide option to ignore underscores.

Implement the possible improvement listed in the comment on
from_str_bytes_common.
libsyntax: fail lexing with an error message on an int literal larger than 2^64.

Stops an ICE.

Closes #5544.
Put AUTHORS.txt file in the release tarball
Update license terms in manpage
auto merge of #5760 : klutzy/rust/vim, r=thestinger

1. disable nested comment which is not supported now
2. add syntax highlight for rustCommentDoc e.g. `/** doc */` or `/// doc`.
auto merge of #5775 : pavpanchekha/rust/patch-1, r=thestinger

Change wrong field name in "Trait Inheritance" section.
auto merge of #5776 : dbaupp/rust/syntax-parse-large-number, r=thestinger

Addresses #5544 and #5770, as well as a comment left in the documentation of `from_str_bytes_common`, so that there is now an option to ignore underscores.
auto merge of #5777 : lucab/rust/lucab/doc/misc, r=thestinger

A non-code PR to put the AUTHORS.txt file in the released tarball and to update the copyright terms in the rustc manpage as per post-dual-licensing.
clone: managed boxes need to clone by shallow copy

Performing a deep copy isn't ever desired for a persistent data
structure, and it requires a more complex implementation to do
correctly. A deep copy needs to check for cycles to avoid an infinite
loop.
auto merge of #5763 : thestinger/rust/clone, r=nikomatsakis

Performing a deep copy isn't ever desired for a persistent data
structure, and it requires a more complex implementation to do
correctly. A deep copy needs to check for cycles to avoid an infinite
loop.
Removing some mutable fields in libstd
Removing no longer needed unsafe blocks