Interesting. Seems like the Go compiler hasn't gotten to the stage of good optimization of "_"... there are quite a few more assembly instructions when using the dual '_, v :=' value assignments.