allow types to be used as methods in less, edit
base/range.jl: generic changes to pave way for FloatRange support.
hashing: port core hashing code from C to pure Julia.

This is in preparation for more drastic hashing changes, but this
change should have zero effect on behavior.
implement proper rounding for Float32 to Float16 conversion

before we always rounded towards zero, now we round to nearest and round
ties to even.

without this, printing Float16s was broken:

```
julia> nextfloat(float16(.3325))
float16(0.3325)

julia> float16(0.3325)
float16(0.3323)
```
Merge branch 'master' of github.com:JuliaLang/julia
update Chinese doc url

Now use `zh_CN` locale, without the this fix, the link would not resolve to the right url
cc @jiahao
remove ill-advised old set constructor. closes #5910
Merge pull request #5888 from simonbyrne/typeless

allow types to be used as methods in less, edit
Merge pull request #5909 from wlbksy/patch-1

update Chinese doc url
make float16 serializable
Restore non-broadcasting +, -, etc. for ranges

I think these were accidentally removed in
9e9ab5c10d8ce4e49c9f9182315e7acd7959c5f5
Updated package list
fix #5912
Merge pull request #5916 from amitmurthy/amitm/f16

make float16 serializable/deserializable
Float16: convert to various number types; round, trunc, floor, ceil.

These additional operations are needed to get the random and linalg
tests closer to passing for the FloatRange change [#5636]. We really
need to make a decision about how first-class we want Float16 to be.
I'm starting to suspect that we should just bite the bullet and make
all the things that work for other floating-point types work for the
Float16 type also. It's just easier than having them be half-broken
and try to explain that they're "just for storage".
fix regression in bitmix() in 3af1dc9a94cbdc7d88ec59f7cf312b4dc0122e15
Float16: dial back on conversions from Float16.
FloatRange type: correct/intuitive floating-point ranges (no syntax).

This addresses the core behvaioral problems of #2333 but doesn't yet
hook up the colon syntax to constructing FloatRange objects [#5885].
FloatRange: hook new type up to colon syntax [fixes #2333].
FloatRange: slightly more conservative test for lifting in frange.

There's a slight chance that computing `stop` with integers and then
converting to floating point would work but doing to computation in
floating point would not give the correct answer. This tests actual
values – with the correct type – that will be used.