Considering the map is declared as value type of V using T below is confusing. I would either remove the example entirely or change it to V.

I don't see the added value in it's inclusion with respect to map indexing so I am suggesting it be removed.

The both code snippets below will not compile. The top snippet because you can't store an int in a bool, the bottom because it considers ok an int which cannot be used in an if statement.

k := make(map[string]int)

var v, ok  bool = k["asdf"]
	

k := make(map[string]int)

var v, ok  int = k["asdf"]

if(ok){
	fmt.Println(ok)
	fmt.Println(v)
	}

Change https://golang.org/cl/94906 mentions this issue: doc: improve clarity of map index examples

I don't think it is much confusing. The type T is not essential to be a bool, it can be any boolean type (and which is also the map element type).
The 4th example make the cases completed. So keeping it is better than removing it.

@dotaheor, I see now. You are right, thank you.

The ok type is not bool, but untyped bool. Makes sense then.

This, for example, compiles and executes as expected:

	type mybool bool
	m := make(map[string]mybool)
	var v, ok mybool = m[""]
	fmt.Println(v, ok)

I believe issue can be closed then.