Arrays

 

Arrays

primarily they are a building block for slices, 

There are major differences between the ways arrays work in Go and C. In Go,

  • Arrays are values. Assigning one array to another copies all the elements.
  • In particular, if you pass an array to a function, it will receive a copy of the array, not a pointer to it.
  • The size of an array is part of its type. The types [10]int and [20]int are distinct.

The value property can be useful but also expensive; if you want C-like behavior and efficiency, you can pass a pointer to the array.

func Sum(a *[3]float64) (sum float64) {
    for _, v := range *a {
        sum += v
    }
    return
}

array := [...]float64{7.0, 8.5, 9.1}
x := Sum(&array)  // Note the explicit address-of operator

But even this style isn't idiomatic Go. Use slices instead.

Comments

Post a Comment

Popular posts from this blog

Naming convention

  Interface names By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun:  Reader ,  Writer ,  Formatter ,  CloseNotifier  etc. MixedCaps Finally, the convention in Go is to use  MixedCaps  or  mixedCaps  rather than underscores to write multiword names. Getters It's neither idiomatic nor necessary to put  Get  into the getter's name. If you have a field called  owner  (lower case, unexported), the getter method should be called  Owner  (upper case, exported), not  GetOwner . The use of upper-case names for export provides the hook to discriminate the field from the method. A setter function, if needed, will likely be called  SetOwner . Both names read well in practice: owner := obj.Owner() if owner != user {     obj.SetOwner(user) } They even have semantic effect: the visibility of a name outside a package i...
Read more