What’s the difference between pointer and value in struct?

by

Use the form which is most functionally useful for your program. Basically, this means if it’s useful for the value to be nil, then use a pointer.

From a performance perspective, primitive numeric types are always more efficient to copy than to dereference a pointer. Even more complex data structures are still usually faster to copy if they are smaller than a cache line or two (under 128 bytes is a good rule of thumb for x86 CPUs).

When things get a little larger, you need to benchmark if performance concerns you. CPUs are very efficient at copying data, and there are so many variables involved which will determine the locality and cache friendliness of your data, it really depends on your program’s behavior, and the hardware you’re using.

This is an excellent series of articles if you want to better understand the how memory and software interact: “What every programmer should know about memory”.

In short, I tell people to choose a pointer or not based on the logic of the program, and worry about performance later.

  • Use a pointer if you need to pass something to be modified.
  • Use a pointer if you need to determine if something was unset/nil.
  • Use a pointer if you are using a type that has methods with pointer receivers.

More Related Contents:

  1. How do I do a literal *int64 in Go?
  2. Invoking struct function gives “cannot refer to unexported field or method”
  3. Cast a struct pointer to interface pointer in Golang
  4. Test for nil values in nested stucts
  5. Pointers vs. values in parameters and return values
  6. Hiding nil values, understanding why Go fails here
  7. X does not implement Y (… method has a pointer receiver)
  8. How to use global var across files in a package?
  9. ” is pointer to interface, not interface” confusion
  10. How can I store reference to the result of an operation in Go?
  11. Copying a struct containing pointers to CUDA device
  12. How to get the pointer of return value from function call?
  13. My object is not updated even if I use the pointer to a type to update it
  14. Slicing a slice pointer passed as argument
  15. Can the pointer in a struct pointer method be reassigned to another instance?
  16. Why does Go forbid taking the address of (&) map member, yet allows (&) slice element?
  17. Dereferencing a map index in Golang
  18. Why should constructor of Go return address?
  19. Range references instead values
  20. In Go HTTP handlers, why is the ResponseWriter a value but the Request a pointer?
  21. Passing by reference and value in Go to functions
  22. Go equivalent of a void pointer in C
  23. C: pointer to struct in the struct definition
  24. Go embedded struct call child method instead parent method
  25. How to set and get fields in struct’s method
  26. Why struct fields are showing empty?
  27. Array of size 0 at the end of struct [duplicate]
  28. Convert slice of string to slice of pointer to string
  29. Returning a struct pointer
  30. How to filter fields from a mongo document with the official mongo-go-driver

Leave a Comment