You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.7 windows/amg64
What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=c:\projects\clarity\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
What did you do?
Compared the runtime of a standard for loop vs a range for loop with the following code:
Thank you, a testing.Benchmark test did reveal the runtime to be the same, and in my benchmark reversing the order of the tests also swapped the runtime. I'll close this.
Please answer these questions before submitting your issue. Thanks!
go version
)?1.7 windows/amg64
go env
)?set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=c:\projects\clarity\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
Compared the runtime of a standard for loop vs a range for loop with the following code:
I am told runtime should be identical, or nearly so
Runtime starts out ~4 times slower for the range loop on the first pass, then ~2x slower thereafer.
The text was updated successfully, but these errors were encountered: