Generate random BigUints and BigInts
test the correct function (oops)
Convert between BigInts and BigUints
Forgot to make accept() home for IO
Make I/O tests use run_in_mt_newsched_task to get more multi-threaded test coverage
Incorporate feedback from huonw

- use identifiers with underscores to avoid unused variable warning
- implement on R: Rng instead of on R: RngUtil
- bugfix: zero BigInts were being generated twice as often as any
  other number
- test that gen_biguint(0) always returns zero
Add with_mem_writer to std::rt::io::mem.

This is in many ways a replacement for the current
std::io::with_str_writer.
Update for_expr docs.
Fix pretty-printing of empty impl items
Convert between BigInts, BigUints, ints, and uints

Previously, conversion to ints, uints, and BigUints clamped the value
within the range of that datatype. With this commit, conversion
overflows fail the task. To handle overflows gracefully, use the new
to_*_opt() methods.
Merge RandBigUint and RandBigInt into single trait
Remove oldvisit.rs (yay!); part of #7081 refactoring.
debuginfo: Wrapped namespace facilities of llvm::DIBuilder
debuginfo: Support for namespaces (functions only)
debuginfo: Support for namespaces for types
rustpkg: Pass command-line arguments to rustc

rustpkg now accepts most of rustc's command-line arguments and passes
them along to rustc when building or installing.

A few rarely-used arguments aren't implemented yet.

rustpkg doesn't support flags that don't make sense with rustpkg
(for example, --bin and --lib, which get inferred from crate file names).

Closes #8522
Implement the notion of a "generated unsafe block"

This way syntax extensions can generate unsafe blocks without worrying about
them generating unnecessary unsafe warnings. Perhaps a special keyword could be
added to be used in macros, but I don't think that's the best solution.
Flag unsafe blocks from format! as compiler-generated
auto merge of #9013 : alexcrichton/rust/generated-unsafe-blocks, r=sanxiyn

This way syntax extensions can generate unsafe blocks without worrying about them generating unnecessary unsafe warnings. Perhaps a special keyword could be added to be used in macros, but I don't think that's the best solution.

Currently if you use `format!` and friends in an `unsafe` block you're guaranteed to get some unused-unsafe warnings which is unfortunate. We normally do want these warnings, but I'm ok ignoring them in the case of compiler-generated unsafe blocks. I tried to do this in the least intrusive way possible, but others may have better ideas about how to do this.
auto merge of #9093 : pnkfelix/rust/fsk-remove-oldvisit, r=alexcrichton