Remove FIXME #2699---I believe the calculation is correct. Fixes #2699.
add jemalloc to the runtime
integrate jemalloc into the build
Windows fixes
mk: Bulid rustrt with -pthread instead of -lpthread
std: work-around for take/skip type inference (#6967)
test/compile-fail: clarify bad-for-loop

There are two distinct kinds of bad-for-loops to check for with two
distinct error messages.  The current bad-for-loop.rs does not make this
clear, so rewrite it into bad-for-loop{,-2}.rs.  The two failing
prototypes are:

  fn quux(_: &fn(&int) -> int) -> bool { true }
  fn quux(_: &fn(&int) -> bool) -> () { }

Note that the second one runs fine in rust-0.6 (the latest release), and
only fails with a rust built from `incoming`.

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
tutorial: fix for-loop example

Although in the example function `each` works as expected with
rust-0.6 (the latest release), it fails to even compile with `incoming`
rust (see test/compile-fail/bad-for-loop-2.rs). Change the function to
return a `bool` instead of `()`: this works fine with both versions of
rust, and does not misguide potential contributors.

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
auto merge of #6972 : artagnon/rust/bad-for-loop, r=bstrie

I noticed this while reading the tutorial.

[1/2] adds tests to guard against regressions.
[2/2] corrects the tutorial.

Please let me know if you have a standard place to put tests: they seem to be all over the place currently.
auto merge of #6975 : artagnon/rust/tuple-tostr, r=bstrie

[1/2] fixes a couple of comments.
[2/2] uses fmt! instead of hand-concatenating strings in a couple of places.

No functional changes.
auto merge of #6968 : huonw/rust/takeskip-iter, r=thestinger

@thestinger r?

Adding the dummy parameter stops the inference from having to work so hard.
Clean up a handful of build warnings.
libc: omit memcpy, memmove and memset

LLVM provides these functions as intrinsics, and will generate calls to
libc when appropriate. They are exposed in the `ptr` module as
`copy_nonoverlapping_memory`, `copy_memory` and `set_memory`.
auto merge of #6937 : msullivan/rust/no-warnings, r=bstrie
Added iter::FromIter
Added IteratorUtil::collect
Removed IteratorUtil::to_vec and iter::to_vec
Fixups
auto merge of #6053 : nikomatsakis/rust/fixme-2699, r=thestinger

r? @jld or @graydon

The calculation looks right to me, but perhaps one of you two can double check.  You two seem like you are doing the most recent work in this sort of area.
add test cases for fold traversing macros