Using go1.5
The hash/* libraries output a slice with the hash in big endian byte order when the Hash.Sum([]byte) method is called. This is fine, but it should be documented.
This does not apply to crypto hashes since those hashes are long enough (and don't fit in native integer types) that nobody mistakes the byte order.
Using
go1.5The hash/* libraries output a slice with the hash in big endian byte order when the Hash.Sum([]byte) method is called. This is fine, but it should be documented.
This does not apply to crypto hashes since those hashes are long enough (and don't fit in native integer types) that nobody mistakes the byte order.