how to understand a reflect.ValueOf is addressable ？

[Hyvi]

 x := 2

a := reflect.ValueOf(x) //no variable 

b := reflect.ValueOf(&x) //no variable 

c := reflect.ValueOf(&x).Elem() //yes variable 

WHY c is addressable? but a and b not 

[Ian Lance Taylor]

On Tue, Jun 25, 2019 at 5:57 PM Hyvi <tanhai...@gmail.com> wrote:
>
> x := 2
> a := reflect.ValueOf(x) //no variable

This is the value of the constant 2, which is not addressable.

> b := reflect.ValueOf(&x) //no variable

This is the value of a pointer, which need not be addressable. For
example, given a map[int]*byte, the value of map[0] is not
addressable.

> c := reflect.ValueOf(&x).Elem() //yes variable

Here the Elem method called on the pointer knows that the returned
value has an address: it's the pointer that was dereferenced. So this
is addressable.

It may help to read https://blog.golang.org/laws-of-reflection .

Ian