Range references instead values

by

The short & direct answer: no, use the array index instead of the value

So the above code becomes:

package main

import "fmt"

type MyType struct {
    field string
}

func main() {
    var array [10]MyType

    for idx, _ := range array {
        array[idx].field = "foo"
    }

    for _, e := range array {
        fmt.Println(e.field)
        fmt.Println("--")
    }
}

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. Why is the return type of Deref::deref itself a reference?
  10. My object is not updated even if I use the pointer to a type to update it
  11. Invoking struct function gives “cannot refer to unexported field or method”
  12. Slicing a slice pointer passed as argument
  13. Cast a struct pointer to interface pointer in Golang
  14. Can the pointer in a struct pointer method be reassigned to another instance?
  15. Why does Go forbid taking the address of (&) map member, yet allows (&) slice element?
  16. Dereferencing a map index in Golang
  17. why slice values can sometimes go stale but never map values?
  18. Why should constructor of Go return address?
  19. In Go HTTP handlers, why is the ResponseWriter a value but the Request a pointer?
  20. Passing by reference and value in Go to functions
  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. What are the differences between a pointer variable and a reference variable in C++?
  25. Reason to Pass a Pointer by Reference in C++?
  26. error: invalid initialization of non-const reference of type ‘int&’ from an rvalue of type ‘int’
  27. How can I instantiate a non-nil pointer of type argument with generic Go?
  28. Why do some people prefer “T const&” over “const T&”?
  29. Why is a c++ reference considered safer than a pointer?
  30. Pass by pointer & Pass by reference [duplicate]

Leave a Comment