A map entry cannot be addressed (as its address might change during map growth/shrink), so you cannot call pointer receiver methods on them.
Detail here: https://groups.google.com/forum/?fromgroups=#!topic/golang-nuts/4_pabWnsMp0
More Related Contents:
- Pointers vs. values in parameters and return values
- Hiding nil values, understanding why Go fails here
- X does not implement Y (… method has a pointer receiver)
- How do I do a literal *int64 in Go?
- How to use global var across files in a package?
- ” is pointer to interface, not interface” confusion
- How can I store reference to the result of an operation in Go?
- How to get the pointer of return value from function call?
- My object is not updated even if I use the pointer to a type to update it
- Invoking struct function gives “cannot refer to unexported field or method”
- Slicing a slice pointer passed as argument
- Cast a struct pointer to interface pointer in Golang
- Can the pointer in a struct pointer method be reassigned to another instance?
- Why does Go forbid taking the address of (&) map member, yet allows (&) slice element?
- Why should constructor of Go return address?
- Range references instead values
- In Go HTTP handlers, why is the ResponseWriter a value but the Request a pointer?
- Passing by reference and value in Go to functions
- Go equivalent of a void pointer in C
- What’s the difference between pointer and value in struct?
- Test for nil values in nested stucts
- Using the extra 16 bits in 64-bit pointers
- Value receiver vs. pointer receiver
- Using Pointers in a for loop
- Copying a struct containing pointers to CUDA device
- Why is the return type of Deref::deref itself a reference?
- Meaning of ‘&variable’ in arguments/patterns
- How can I instantiate a non-nil pointer of type argument with generic Go?
- Return pointer to local struct
- Convert slice of string to slice of pointer to string