Fixes #7377
configure: Require one of wget or curl.
When an impl references an unknown trait, mention what
the trait is called in the error message.
Add an EnumSetIterator and EnumSet::iter
Move most iter functionality to extra, fixes #7343
extra: docs, tests and new functionality for the extra::stats module
librustc: back::link::sanitize support esacpe_utf8
librustc: apply changes of char::escape_unicode
lint: make the non_camel_case_types lint work with scripts without a upper/lowercase distinction.
rustc: add a lint to enforce uppercase statics.
auto merge of #7443 : yjh0502/rust/fix_field_dup, r=huonw

Check if there is duplicated field names in struct.
auto merge of #7488 : yichoi/rust/sanitize_utf8, r=huonw

back::link::sanitize support escape_utf8
fix #7486
Turn on using LLVM threadsafely
auto merge of #7409 : alexcrichton/rust/threadsafe, r=cmr

@catamorphism, this re-enables threadsafe rustpkg tests, @brson this will fail unless the bots have LLVM rebuilt, so this is a good indicator of whether that happened or not.
Improve the attempted dynamic environment-capture error message
Better error messages in report_use_of_moved_value; close #7286
Fix filenames of some compile-fail tests.
Add a run-pass test for recursive copyable stack closures.
Defer reasoning about region relationships until after regionck.

This patch makes error handling for region inference failures more
uniform by not reporting *any* region errors until the reigon inference
step. This requires threading through more information about what
caused a region constraint, so that we can still give informative
error messages.

I have only taken partial advantage of this information: when region
inference fails, we still report the same error we always did, despite
the fact that we now know precisely what caused the various constriants
and what the region variable represents, which we did not know before.

This change is required not only to improve error messages but
because the region hierarchy is not in fact fully known until regionck,
because it is not clear where closure bodies fit in (our current
treatment is unsound). Moreover, the relationships between free variables
cannot be fully determined until type inference is otherwise complete.

cc #3238.
Correct handling of if/match, and make explicit computation of
common supertypes.

This was breaking with the change to regions because of the
(now incorrect) assumpton that our inference code makes,
which is that if a <: b succeeds, there is no need to compute
the LUB/GLB.