Remove incorrect assert in trans

As an optimization, once unboxed closures receive their environment by
value if it fits within the size of an `int`.  An assert in this code
path assumed that this would only occur if the environment had no more
than a single free variable in it, but multiple smaller free variables
can easily be packed into the space of an `int`, particularly if any
of them are 0-sized.  The assert can simply be removed.

Closes #18652
Add regression test for #18652
Derive Clone for TypeId.
Remove unnecessary `.to_string()`s from `Vec.swap_remove`'s doc example.
Properly static lib packaging

Fixes #18574
Prepend should be append in the 30 minute intro

The examples are about adding to the end of the array, not the
beginning.
rustc: Process #[cfg]/#[cfg_attr] on crates

This commit implements processing these two attributes at the crate level as
well as at the item level. When #[cfg] is applied at the crate level, then the
entire crate will be omitted if the cfg doesn't match. The #[cfg_attr] attribute
is processed as usual in that the attribute is included or not depending on
whether the cfg matches.

This was spurred on by motivations of #18585 where #[cfg_attr] annotations will
be applied at the crate-level.

cc #18585
Make TyTrait embed a `TraitRef`, so that when we extend TraitRef, it naturally carries over to object types.

I wanted to embed an `Rc<TraitRef>`, but I was foiled by the current
static rules, which prohibit non-Sync values from being stored in
static locations. This means that the constants for `ty_int` and so
forth cannot be initialized.
Update parser with `for` syntax
Update tests where we don't report errors twice anymore
Purge the old `once_fns`, which are not coming back
Fix tidy error
Implement len() for EnumSet.
Add BitXor to EnumSet.
syntax: Use UFCS in the expansion of `#[deriving(PartialOrd)]`
Add tests for BitAnd and BitXor.
Update Partial/Total Eq/Ord terminology
Reword &str coercion into viewing
auto merge of #18634 : alexcrichton/rust/cfg-attr-crate-level, r=sfackler

This commit implements processing these two attributes at the crate level as
well as at the item level. When #[cfg] is applied at the crate level, then the
entire crate will be omitted if the cfg doesn't match. The #[cfg_attr] attribute
is processed as usual in that the attribute is included or not depending on
whether the cfg matches.

This was spurred on by motivations of #18585 where #[cfg_attr] annotations will
be applied at the crate-level.

cc #18585
auto merge of #18731 : chris-morgan/rust/derive-Clone-for-TypeId, r=alexcrichton