mk: target triple rename arm-unknown-android->arm-linux-androideabi
Represent enums with regular structs; no more alignment-breaking casts.
Refactored sudoku benchmark to use traits and added some tests
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.
Update rust.vim

Column limit 78 -> 100.
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.
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.
auto merge of #5412 : pcwalton/rust/purity, r=pcwalton

 	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.

r? @nikomatsakis
Allow constant expressions in [Type * n].
Now actually allow using constants in those constant expressions for [T * n].
Allow expressions that are not just a single value for repeated fixed length vector syntax.
Fix pretty printer for fixed length vectors.
Add tests for const exprs in fixed vec length type and vec repeat.
Make driver::driver::parse_cfgspecs parse any variety of meta_item

All current meta items types (word, name-value, list) are now
properly parsed by rustc --cfg command line. Fixes #2399

Signed-off-by: Luca Bruno <lucab@debian.org>
auto merge of #5112 : luqmana/rust/3469, r=graydon

So this is a partial fix for #3469. Partial because it only works for simple constant expressions like `32/2` and `2+2` and not for any actual constants.

For example:
```
const FOO: uint = 2+2;
let v: [int * FOO];
```

results in:
```
error: expected constant expr for vector length: Non-constant path in constant expr
```

This seems to be because at the point of error (`typeck::astconv`) the def_map doesn't contain the constant and thus it can't lookup the actual expression (`2+2` in this case).

So, feedback on what I have so far and suggestions for how to address the constant issue?