use LIBUV_INC so that USE_SYSTEM_LIBUV works
make ranges and arrays unequal, faster hashing of ranges, fixes #5778

fix == and isequal of ranges to only compare by components when it is safe to do so
  (ranges with different types but == components can generate different elements)

add float32(x) etc. for FloatRange

don't show floating point Range objects using colons, since those construct FloatRanges
Fix A_mul_B! for y inputs with NaNs by setting elements to zero when β is zero.
grammar
fix #6098, crash on stack overflow splicing big argument lists

still slow as hell and still a bad idea, but at least it doesn't segfault
fix #6099, small oversight that left out .+= and .-=
fix #6091, message for non-finite or length mismatch in test_approx_eq
Which for error message for non-broadcasting (+) and (-)
mitigate #6097

the general problem was that one place in the code had a larger type for
a tuple than another. I don't know why, but we can at least generate
correct code instead of crashing. there was already some code in boxed()
towards handling this kind of thing, but it needed to be rearranged a bit.
type stability in all norm variants (continuing #6056 and #6057)
Doc for lufact is corrected and updated.

- lufact(::Tridiagonal) is now documented.
- Tabulate the output types LU, LUTridiagonal and UmfpackLU types, their components, and supported methods.
Merge pull request #6084 from JuliaLang/jb/equalranges

make ranges and arrays unequal, faster hashing of ranges, fixes #5778
Merge pull request #6100 from ivarne/patch-1

Which for error message for non-broadcasting (+) and (-)
explicitly return nothing from runtests
try harder to resolve tangles of module re-exports. fixes #6105

Say module A uses module D and others. It will first try to resolve
an identifier using D. If D imports the identifier from A, jl_get_binding_
will return NULL due to a cycle. Before, we considered the identifier
undefined at that point. Now we keep looking in subsequent `using`
modules.

The reason I didn't do this before is that it can cause us to dig deeper
into the using list, and possibly find an identifier that should be
shadowed by other usings. But this is only a problem if the same
identifier is provided by two different usings, which is already ambiguous
and deserves more serious treatment.
Merge pull request #6109 from tkelman/patch-3

Explicitly return nothing from runtests
remove randsym from doc
set CPU_CORES only at startup and not during build. fixes #6102
Merge branch 'master' of github.com:JuliaLang/julia
Merge pull request #6101 from stevengj/stablenorm

fix type stability in all norm variants