CL https://golang.org/cl/20654 mentions this issue.

Is this a duplicate of #5364 ? Both seem like tracking issues.

A case that maybe could be added to the doc above and loopbce.go is when writing to an array/slice from back to front e.g. for integer formatting:

for i = len(buf) - 1; i >= 0; i-- {
    if u < 10 {
        buf[i] = byte('0' + u)
        break
    }
    next := u / 10
    buf[i] = byte('0' + u - next*10)
    u = next
}

This currently generates bounds checks but when writing the above with i = 0; i < len(buf); i++ the bounds checks are removed.

https://play.golang.org/p/epAcCz9W-Uu
=>
https://godbolt.org/z/vl_rTS

If you have four slice indexing operations in a single expression, with constant indexes, it should be possible to combine them.

Change https://golang.org/cl/202517 mentions this issue: encoding/binary: removal of unnecessary boundary checks.