Passing by reference and value in Go to functions

by

First, Go technically has only pass-by-value. When passing a pointer to an object, you’re passing a pointer by value, not passing an object by reference. The difference is subtle but occasionally relevant. For example, you can overwrite the pointer value which has no impact on the caller, as opposed to dereferencing it and overwriting the memory it points to.

// *int means you *must* pass a *int (pointer to int), NOT just an int!
func someFunc(x *int) {
    *x = 2 // Whatever variable caller passed in will now be 2
    y := 7
    x = &y // has no impact on the caller because we overwrote the pointer value!
}

As to your question “Why do we need to have the asterisk in front of the type?”: The asterisk indicates that the value is of type pointer to sql.DB, rather than a value of type sql.DB. These are not interchangeable!

Why would you want to send a pointer address? So that you can share the value between the caller of a function and the function body, with changes made inside the function reflected in the caller (for example, a pointer is the only way that a “setter” method can work on an object). While Java passes objects by reference always, Go passes by value always (i.e. it creates a copy of the value in the function); if you pass something to a function, and that function modifies that value, the caller won’t see those changes. If you want changes to propogate outside the function, you must pass a pointer.

See also: the Go tour section on Pointers, the Go spec section on pointers, the Go spec section on the address operators

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. Why does Go forbid taking the address of (&) map member, yet allows (&) slice element?
  15. Dereferencing a map index in Golang
  16. Why should constructor of Go return address?
  17. Range references instead values
  18. In Go HTTP handlers, why is the ResponseWriter a value but the Request a pointer?
  19. Go equivalent of a void pointer in C
  20. What’s the difference between pointer and value in struct?
  21. Test for nil values in nested stucts
  22. Copying a struct containing pointers to CUDA device
  23. Why does printing a pointer print the same thing as printing the dereferenced pointer?
  24. Should pointer comparisons be signed or unsigned in 64-bit x86?
  25. Meaning of ‘&variable’ in arguments/patterns
  26. why slice values can sometimes go stale but never map values?
  27. How can I instantiate a non-nil pointer of type argument with generic Go?
  28. How to check if two variables point to the same object in memory?
  29. Kotlin function parameter: Val cannot be reassigned
  30. What do “value semantics’” and “pointer semantics” mean in Go?

Leave a Comment