From charlesreid1

 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
Go blog post: arrays, slices, and strings: https://blog.golang.org/slices
Go blog post: arrays, slices, and strings: https://blog.golang.org/slices


=Arrays in Go=
=Basics=


"Arrays are not often seen in Go programs because the size of an array is part of its type, which limits its expressive power."
==Initialization==
 
The most common use of arrays are to store slices, which we will see in a moment.
 
==Array size is a part of the type==


An important characteristic of arrays is that their size is a part of their type.
The most important thing to understand about arrays is that they are different from slices.


The two variables defined here are of two distinct types:
If we create the variable like this:


<pre>
<pre>
var buffer [256]byte
var keys [3]int
var buffer2 [512]byte
</pre>
</pre>


This is because the size of the array is allocated at initialization time. You can use the square bracket syntax to access elements of an array, <code>buffer[0]</code> through <code>buffer[255]</code>. The program crashes if you access an index outside of its range.
it is an array type. That's because we've specified the precise capacity that keys should have.
 
==Array slices==
 
The bracket notation with colons can be used to refer to a slice of an array. For example:
 
<pre>
var buffer [256]byte
...
var slice []byte = buffer[100:150]
</pre>


alternatively,
But if we create the variable like this:


<pre>
<pre>
slice := buffer[100:150]
var keys []int
</pre>
</pre>


Think of a slice variable as a data structure with two elements: a length, and a pointer to an element of the array.
it is a slice type. That's because we did not specify the capacity.


We can also take a slice of the slice:
In both cases, we have not actually initialized the value of either variable. Here's how we create an array:


<pre>
<pre>
slice2 := slice[5:10]
keys := [3]int{10,20,30}
</pre>
</pre>


Here's a shortcut to drop the first and last elements:
==Array size is a part of the type==


<pre>
An important characteristic of arrays is that their size is a part of their type.
slice3 := slice[1:len(slice)-1]
</pre>


===References vs Copies===
"Arrays are not often seen in Go programs because the size of an array is part of its type, which limits its expressive power."


It is important to distinguish between the slice data structure, which is a small bundle that contains a reference to the underlying array data and a length, and the underlying array data itself.
The two variables defined here are of two distinct types:
 
if we use a slice to modify the underlying array data, those changes will be persistent across functions and scopes. But if we modify the slice variable directly, we are modifying a copy of the slice data structure, and we will discard that copy when we leave that scope.
 
===Example modifying underlying array data===
 
The following example modifies the underlying array data:


<pre>
<pre>
func AddOneToEachElement(slice []byte) {
var buffer [256]byte
    for i := range slice {
var buffer2 [512]byte
        slice[i]++
    }
}
 
func main() {
    slice := buffer[10:20]
    for i := 0; i < len(slice); i++ {
        slice[i] = byte(i)
    }
    fmt.Println("before", slice)
    AddOneToEachElement(slice)
    fmt.Println("after", slice)
}
</pre>
</pre>


Again, this requires us to think about the array slice as a data structure, which contains a pointer to an array and a length. The bundle, the data structure, is not a pointer itself!
This is because the size of the array is allocated at initialization time. You can use the square bracket syntax to access elements of an array, <code>buffer[0]</code> through <code>buffer[255]</code>. The program crashes if you access an index outside of its range.


Even though the slice (also called the "slice header") is passed by value, the header includes a pointer to elements of an array. Thus, both the original and the copy passed to the function refer to the same underlying array (slots in memory).
==Array slices==
 
===Example modifying copy of slice===
 
The argument to the SubtractOneFromLength function is a slice, which in this case is a copy of the original slice data structure, containing a reference to the same underlying data.
 
When we modify the slice variable directly, those changes only affect the copy of the data slice, so the original slice is not affected.
 
<pre>
func SubtractOneFromLength(slice []byte) []byte {
    slice = slice[0 : len(slice)-1]
    return slice
}
 
func main() {
    fmt.Println("Before: len(slice) =", len(slice))
    newSlice := SubtractOneFromLength(slice)
    fmt.Println("After:  len(slice) =", len(slice))
    fmt.Println("After:  len(newSlice) =", len(newSlice))
}
</pre>
 
 
===Array Slice Capacity===
 
The capacity of an array is fixed; to make a new array with a new capacity, use the make() function.
 
The make function allocates space in memory for an array slice with a specified capacity.
 
The make function takes three arguments: the type of the slice, its initial length, and its capacity, which is the length of the array that make allocates to hold the slice data.


<pre>
See [[Go/Slices]]
// Make an array slice with a length of 100 and room for 5 more
slice := make([]int, 100, 15)
</pre>


To double the array slice capacity:
==Comparison==


<pre>
Let's cover how to compare arrays.
    // Original slice:
    slice := make([]int, 10, 15)
    fmt.Printf("len: %d, cap: %d\n", len(slice), cap(slice))


    // New slice (double the capacity):
Array values are comparable if values of the array element type are comparable.
    newSlice := make([]int, len(slice), 2*cap(slice))
    for i := range slice {
        newSlice[i] = slice[i]
    }


    // Replace old with new
Two array values are equal if their corresponding elements are equal.
    slice = newSlice
    fmt.Printf("len: %d, cap: %d\n", len(slice), cap(slice))
</pre>


The above code is functional but awkward; Go provides a copy function to copy an old array into a new array, to accomplish the above in fewer lines.
However, note that you cannot compare slices: https://play.golang.org/p/Kk8osjPm8n


<pre>
Likewise: https://play.golang.org/p/kCVoPekPudc
newSlice := make([]int, len(slice), 2*cap(slice))
copy(newSlice, slice)
</pre>


=Flags=
=Flags=


{{GoFlag}}
{{GoFlag}}

Latest revision as of 18:09, 14 December 2018

Go blog post: arrays, slices, and strings: https://blog.golang.org/slices

Basics

Initialization

The most important thing to understand about arrays is that they are different from slices.

If we create the variable like this:

var keys [3]int

it is an array type. That's because we've specified the precise capacity that keys should have.

But if we create the variable like this:

var keys []int

it is a slice type. That's because we did not specify the capacity.

In both cases, we have not actually initialized the value of either variable. Here's how we create an array:

keys := [3]int{10,20,30}

Array size is a part of the type

An important characteristic of arrays is that their size is a part of their type.

"Arrays are not often seen in Go programs because the size of an array is part of its type, which limits its expressive power."

The two variables defined here are of two distinct types:

var buffer [256]byte
var buffer2 [512]byte

This is because the size of the array is allocated at initialization time. You can use the square bracket syntax to access elements of an array, buffer[0] through buffer[255]. The program crashes if you access an index outside of its range.

Array slices

See Go/Slices

Comparison

Let's cover how to compare arrays.

Array values are comparable if values of the array element type are comparable.

Two array values are equal if their corresponding elements are equal.

However, note that you cannot compare slices: https://play.golang.org/p/Kk8osjPm8n

Likewise: https://play.golang.org/p/kCVoPekPudc

Flags