Not urgent in any way but marked as 1.10 so it doesn't slip from the radar. Might be an easy fix.

There is a paradox

package main

import "unsafe"

const (
	i = 1
	j
	k
	x = unsafe.Sizeof(func() {const a = iota; var _ [a-2]int }) // a is 0 or 3?
	y
	z
)

func main() {
}

The current gc thinks a is 0.

const a = iota sets a to 0.

@go101 This "paradox" was addressed with the most recent changes for #15550. The value of iota is the index of the respective ConstSpec in the constant declaration. Here you have a constant declaration inside the function, and the iota is in the first ConstSpec of that constant declaration, which has index 0. Hence the value of iota and thus a is 0.

Change https://golang.org/cl/194717 mentions this issue: cmd/compile: allow iota inside function in a ConstSpec