Issue #5967: Make rvalues mutable
Add explanatory comment to is_rvalue_or_immutable()
Implement bytes! syntax extension
Add a test for bytes!
main() is in ./rustc.rc. use "./../" pattern some more
syntax: implement #[deriving(DeepClone)]. Fixes #6514.
auto merge of #6531 : sammykim/rust/bytes, r=luqmana

Fix #4334.
syntax: use fmt! over + in deriving/clone
auto merge of #6530 : huonw/rust/deriving-deepclone, r=bstrie
Add BuiltinBounds to closure type: parse and handle subtyping,
but do not integrate with kindck etc (requires a snapshot first)
auto merge of #6457 : nikomatsakis/rust/issue-6308-closure-bounds, r=brson

Add BuiltinBounds to closure type: parse and handle subtyping,
but do not integrate with kindck etc (requires a snapshot first)

r? @brson
core: Document some intrinsics
Add two tests for rvalue mutability
correct typo
auto merge of #6473 : nikomatsakis/rust/issue-5967-rvalue-immutability, r=pcwalton

Simpler version of PR #5974 based on new borrowck.
auto merge of #6536 : kud1ing/rust/patch-1, r=brson
rustc: Change ty::get_impl_traits to return an option instead of a vec

Impls can implement either zero or one traits; this has been true
more or less since we removed classes. So I got rid of the comments
saying "we should support multiple traits" and changed the code to
make it clear that we don't. This is just cleanup, and doesn't break
any existing tests.
auto merge of #6543 : catamorphism/rust/traits-cleanup, r=nikomatsakis

r? @nikomatsakis Impls can implement either zero or one traits; this has been true
more or less since we removed classes. So I got rid of the comments
saying "we should support multiple traits" and changed the code to
make it clear that we don't. This is just cleanup, and doesn't break
any existing tests.
rustc: One less bad copy
rustc: Remove import that is, indeed, not necessary