Why does Go forbid taking the address of (&) map member, yet allows (&) slice element?

by

There is a major difference between slices and maps: Slices are backed by a backing array and maps are not.

If a map grows or shrinks a potential pointer to a map element may become a dangling pointer pointing into nowhere (uninitialised memory). The problem here is not “confusion of the user” but that it would break a major design element of Go: No dangling pointers.

If a slice runs out of capacity a new, larger backing array is created and the old backing array is copied into the new; and the old backing array remains existing. Thus any pointers obtained from the “ungrown” slice pointing into the old backing array are still valid pointers to valid memory.

If you have a slice still pointing to the old backing array (e.g. because you made a copy of the slice before growing the slice beyond its capacity) you still access the old backing array. This has less to do with pointers of slice elements, but slices being views into arrays and the arrays being copied during slice growth.

Note that there is no “reducing the backing array of a slice” during slice shrinkage.

More Related Contents:

  1. Pointers vs. values in parameters and return values
  2. Hiding nil values, understanding why Go fails here
  3. X does not implement Y (… method has a pointer receiver)
  4. How do I do a literal *int64 in Go?
  5. How to use global var across files in a package?
  6. ” is pointer to interface, not interface” confusion
  7. How can I store reference to the result of an operation in Go?
  8. How to get the pointer of return value from function call?
  9. My object is not updated even if I use the pointer to a type to update it
  10. Invoking struct function gives “cannot refer to unexported field or method”
  11. Slicing a slice pointer passed as argument
  12. Cast a struct pointer to interface pointer in Golang
  13. Can the pointer in a struct pointer method be reassigned to another instance?
  14. Dereferencing a map index in Golang
  15. Why should constructor of Go return address?
  16. How to check if two variables point to the same object in memory?
  17. Range references instead values
  18. In Go HTTP handlers, why is the ResponseWriter a value but the Request a pointer?
  19. Passing by reference and value in Go to functions
  20. Convert slice of string to slice of pointer to string
  21. Go equivalent of a void pointer in C
  22. What’s the difference between pointer and value in struct?
  23. Test for nil values in nested stucts
  24. Pointer address in a C multidimensional array
  25. Create new C++ object at specific memory address?
  26. Meaning of ‘&variable’ in arguments/patterns
  27. How can I instantiate a non-nil pointer of type argument with generic Go?
  28. Kotlin function parameter: Val cannot be reassigned
  29. What do “value semantics’” and “pointer semantics” mean in Go?
  30. Both asterisk and ampersand in a parameter

Leave a Comment