mk: target triple rename arm-unknown-android->arm-linux-androideabi
Represent enums with regular structs; no more alignment-breaking casts.
rustdoc: Document explicit self in methods. Closes #5254
syntax: Fix fun_to_str test
rt: Add RUST_DEBUG_MEM to rust_env to avoid races
auto merge of #5342 : brson/rust/debug-mem, r=brson

Fixes #5341
auto merge of #5415 : brson/rust/rustdoc, r=thestinger

r? @thestinger
rustdoc: Fix method printing tests
auto merge of #5374 : z0w0/rust/rustdoc-explicit-self, r=z0w0
Refactored sudoku benchmark to use traits and added some tests
rt: Inline get_sp_limit/set_sp_limit/get_sp for x86_64.
rt: Inline get_sp_limit/set_sp_limit/get_sp for x86.
auto merge of #5420 : boggle/rust/sudoku-with-traits, r=graydon

Came back to look at rust and found out that this had been broken by some refactoring work. Fixed and now has tests.
librustc: Convert all uses of old lifetime notation to new lifetime notation. rs=delifetiming
libsyntax: Stop parsing old lifetimes, except for the ones on data type declarations.
Make &self permit explicit lifetimes, but don't really use them
(this will be needed for snapshotting at some point).
librustc: Make the compiler ignore purity.

For bootstrapping purposes, this commit does not remove all uses of
the keyword "pure" -- doing so would cause the compiler to no longer
bootstrap due to some syntax extensions ("deriving" in particular).
Instead, it makes the compiler ignore "pure". Post-snapshot, we can
remove "pure" from the language.

There are quite a few (~100) borrow check errors that were essentially
all the result of mutable fields or partial borrows of `@mut`. Per
discussions with Niko I think we want to allow partial borrows of
`@mut` but detect obvious footguns. We should also improve the error
message when `@mut` is erroneously reborrowed.
core: Cleanup rt::context
Give core::rt and std::net their own uvll bindings

I intend to do some big refactoring and don't want to deal w/ std just now
core: Don't use printf in rtdebug!

The bots were showing a segfault that I can't reproduce. Assuming it's
varargs related so let's not use printf