I think it's still there.

    package main

    func main() {
        slice := []string{"first", "second", "third"}
        println(slice[1])
        slice = slice[0:2]
        println(slice[2])
    }

Compile with

    go build -gcflags -B wat.go
    ./wat

Output

    second
    third

Without the `-B` you'll get a runtime panic. I'm on Go 1.1. (Maybe it's removed in tip?)

Ah ok, I was trying to locate it via the browser.

Next time I better checkout and do a proper grep.

> So I assume you don't do C or C++. :)

If C had a simple universal switch for bounds checking, I'd turn it on everywhere and immediately revoke commit privileges for anyone on my team who turned it back off. But it doesn't, and necessarily can't, making your statement nothing more than an annoying exercise in wrongful pedantry. It is contextually obvious I was talking about Go code and/or languages/compilers with such a switch.

I was trying you out, because if you make such a statement then I am lead to believe you stay away from languages that don't provide control over bounds checking.