preliminary Linux ARM support
Created utility uninhabited type

In this commit I added a useful utility type, named Void, that encapsulates the
doable but annoying job of creating an uninhabited type. As well, a function on
that type, named absurd, was created which is useful for ignoring the result of
matching on that type. No unit tests were created because it is not possible to
create an instance of this type to test the usage of.

This type is useful because it is like NonCopyable in that it can be used to
create a type with special characteristics without special bloat. For instance,
instead of typing pub struct PhantomType { priv contents : () } for each void
type one may want to use one can simply type pub struct PhantomType (Void);.
This type make such special cases much easier to write.
Remove redundant import error
Add to_str() for HashMaps, and some basic tests as well.
Removed test_hashmap() for the time, being. All tests pass with make check.
All tests, including newly added test_hashmap() pass. The empty Hash Table doesn't need to be mutable.
Remove extra space between key and value.

1. Extra space removed.
2. Using acc.push_str() instead of str::push_str
3. Update test to reflect representation change.
Add str representation for HashSet.
Add test: test_hashset()
Use acc.push_str() instead of str::push_str(..)

Also added some whitespace to enhance readabilty.
Fix errors in test_hashset().

All tests now pass.
rustc: Don't call type_error_message() with ty_err as the expected type

In #6319, several people mentioned they ran into a "computing
fictitious type" ICE in trans. This turns out to be because some
of my recent changes to typeck::check::_match resulted in type errors
getting reported with ty_err as the expected type, which meant the errors
were suppressed, and typechecking incorrectly succeeded (since the errors
weren't recorded).

Changed the error messages in these cases not to use an expected type at all,
rather, printing out a string describing the type that was expected (which is
what the code originally did). The result is a bit repetitive and the
proliferation of error-reporting functions in typeck::infer is a bit annoying,
but I thought it was important to fix this now; more cleanup can happen later.
libstd: Fix BigUint::is_even
Warning police
clean up the last bit of warnings
auto merge of #6431 : catamorphism/rust/warnings, r=catamorphism

Just cleaning up warnings.
auto merge of #6429 : gifnksm/rust/bigint-is_even, r=catamorphism

`BigUint::is_even()` didn't return correct value.
Fix failing test
Add use declaration for container::Set

All tests pass now.
auto merge of #6427 : catamorphism/rust/issue-6319, r=nikomatsakis

r? @nikomatsakis In #6319, several people mentioned they ran into a "computing
fictitious type" ICE in trans. This turns out to be because some
of my recent changes to typeck::check::_match resulted in type errors
getting reported with ty_err as the expected type, which meant the errors
were suppressed, and typechecking incorrectly succeeded (since the errors
weren't recorded).

Changed the error messages in these cases not to use an expected type at all,
rather, printing out a string describing the type that was expected (which is
what the code originally did). The result is a bit repetitive and the
proliferation of error-reporting functions in typeck::infer is a bit annoying,
but I thought it was important to fix this now; more cleanup can happen later.