-
Michael Munday authored
Use the binary.{Big,Little}Endian integer encoding methods rather than unsafe or local implementations. These methods are tested to ensure they inline correctly and don't add unnecessary bounds checks, so it seems better to use them wherever possible. This introduces a dependency on encoding/binary to crypto/cipher. I think this is OK because other "L3" packages already import encoding/binary. Change-Id: I5cf01800d08554ca364e46cfc1d9445cf3c711a0 Reviewed-on: https://go-review.googlesource.com/115555 Run-TryBot: Michael Munday <mike.munday@ibm.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
4a842f25
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
eagain.go | ||
example_test.go | ||
rand.go | ||
rand_js.go | ||
rand_linux.go | ||
rand_linux_test.go | ||
rand_openbsd.go | ||
rand_test.go | ||
rand_unix.go | ||
rand_windows.go | ||
util.go | ||
util_test.go |