Pointers & errors

    We learned about structs in the last section which let us capture a number of values related around a concept.

    At some point you may wish to use structs to manage state, exposing methods to let users change the state in a way that you can control.

    Fintech loves Go and uhhh bitcoins? So let’s show what an amazing banking system we can make.

    Let’s make a struct which let’s us deposit Bitcoin.

    In the previous example we accessed fields directly with the field name, however in our very secure wallet we don’t want to expose our inner state to the rest of the world. We want to control access via methods.

    Try to run the test

    ./wallet_test.go:7:12: undefined: Wallet

    Write the minimal amount of code for the test to run and check the failing test output

    The compiler doesn’t know what a Wallet is so let’s tell it.

    1. type Wallet struct { }

    Now we’ve made our wallet, try and run the test again

    1. ./wallet_test.go:9:8: wallet.Deposit undefined (type Wallet has no field or method Deposit)
    2. ./wallet_test.go:11:15: wallet.Balance undefined (type Wallet has no field or method Balance)

    We need to define these methods.

    Remember to only do enough to make the tests run. We need to make sure our test fails correctly with a clear error message.

    1. func (w Wallet) Deposit(amount int) {
    3. }
    5. func (w Wallet) Balance() int {
    6.     return 0
    7. }

    If this syntax is unfamiliar go back and read the structs section.

    The tests should now compile and run

    wallet_test.go:15: got 0 want 10

    Write enough code to make it pass

    We will need some kind of balance variable in our struct to store the state

    1. type Wallet struct {
    2.     balance int
    3. }

    In Go if a symbol (so variables, types, functions et al) starts with a lowercase symbol then it is private outside the package it’s defined in.

    In our case we want our methods to be able to manipulate this value but no one else.

    Remember we can access the internal balance field in the struct using the “receiver” variable.

    1. func (w Wallet) Deposit(amount int) {
    2.     w.balance += amount
    3. }
    5. func (w Wallet) Balance() int {
    6.     return w.balance
    7. }

    With our career in fintech secured, run our tests and bask in the passing test

    wallet_test.go:15: got 0 want 10

    Well this is confusing, our code looks like it should work, we add the new amount onto our balance and then the balance method should return the current state of it.

    In Go, when you call a function or a method the arguments are copied.

    When calling func (w Wallet) Deposit(amount int) the w is a copy of whatever we called the method from.

    Without getting too computer-sciency, when you create a value - like a wallet, it is stored somewhere in memory. You can find out what the address of that bit of memory with &myVal.

    Experiment by adding some prints to your code

    1. func TestWallet(t *testing.T) {
    3.     wallet := Wallet{}
    5.     wallet.Deposit(10)
    7.     got := wallet.Balance()
    9.     fmt.Printf("address of balance in test is %v \n", &wallet.balance)
    11.     want := 10
    13.     if got != want {
    14.         t.Errorf("got %d want %d", got, want)
    15.     }
    16. }
    1. func (w Wallet) Deposit(amount int) {
    2.     fmt.Printf("address of balance in Deposit is %v \n", &w.balance)
    3.     w.balance += amount
    4. }

    The \n escape character, prints new line after outputting the memory address. We get the pointer to a thing with the address of symbol; &.

    Now re-run the test

    1. address of balance in Deposit is 0xc420012268
    2. address of balance in test is 0xc420012260

    You can see that the addresses of the two balances are different. So when we change the value of the balance inside the code, we are working on a copy of what came from the test. Therefore the balance in the test is unchanged.

    We can fix this with pointers. Pointers let us point to some values and then let us change them. So rather than taking a copy of the Wallet, we take a pointer to the wallet so we can change it.

    1. func (w *Wallet) Deposit(amount int) {
    2.     w.balance += amount
    3. }
    5. func (w *Wallet) Balance() int {
    6.     return w.balance
    7. }

    The difference is the receiver type is *Wallet rather than Wallet which you can read as “a pointer to a wallet”.

    Now you might wonder, why did they pass? We didn’t dereference the pointer in the function, like so:

    and seemingly addressed the object directly. In fact, the code above using (*w) is absolutely valid. However, the makers of Go deemed this notation cumbersome, so the language permits us to write w.balance, without explicit dereference.These pointers to structs even have an own name: struct pointers and they are .

    Refactor

    We said we were making a Bitcoin wallet but we have not mentioned them so far. We’ve been using int because they’re a good type for counting things!

    It seems a bit overkill to create a struct for this. int is fine in terms of the way it works but it’s not descriptive.

    Go lets you create new types from existing ones.

    The syntax is type MyName OriginalType

    1. type Bitcoin int
    3. type Wallet struct {
    4.     balance Bitcoin
    5. }
    7. func (w *Wallet) Deposit(amount Bitcoin) {
    8.     w.balance += amount
    9. }
    11. func (w *Wallet) Balance() Bitcoin {
    12.     return w.balance
    13. }
    1. func TestWallet(t *testing.T) {
    3.     wallet := Wallet{}
    5.     wallet.Deposit(Bitcoin(10))
    7.     got := wallet.Balance()
    8.     want := Bitcoin(10)
    10.     if got != want {
    11.         t.Errorf("got %d want %d", got, want)
    12.     }
    13. }

    To make Bitcoin you just use the syntax Bitcoin(999).

    By doing this we’re making a new type and we can declare methods on them. This can be very useful when you want to add some domain specific functionality on top of existing types.

    Let’s implement on Bitcoin

    1. type Stringer interface {
    2.         String() string
    3. }

    This interface is defined in the fmt package and lets you define how your type is printed when used with the %s format string in prints.

    1. func (b Bitcoin) String() string {
    3. }

    As you can see, the syntax for creating a method on a type alias is the same as it is on a struct.

    Next we need to update our test format strings so they will use String() instead.

    1.     if got != want {
    2.         t.Errorf("got %s want %s", got, want)
    3.     }

    To see this in action, deliberately break the test so we can see it

    wallet_test.go:18: got 10 BTC want 20 BTC

    This makes it clearer what’s going on in our test.

    The next requirement is for a Withdraw function.

    Write the test first

    Pretty much the opposite of Deposit()

    1. func TestWallet(t *testing.T) {
    3.     t.Run("Deposit", func(t *testing.T) {
    4.         wallet := Wallet{}
    6.         wallet.Deposit(Bitcoin(10))
    8.         got := wallet.Balance()
    10.         want := Bitcoin(10)
    12.         if got != want {
    13.             t.Errorf("got %s want %s", got, want)
    14.         }
    15.     })
    17.     t.Run("Withdraw", func(t *testing.T) {
    18.         wallet := Wallet{balance: Bitcoin(20)}
    20.         wallet.Withdraw(Bitcoin(10))
    22.         got := wallet.Balance()
    24.         want := Bitcoin(10)
    26.         if got != want {
    27.             t.Errorf("got %s want %s", got, want)
    28.         }
    29.     })
    30. }

    ./wallet_test.go:26:9: wallet.Withdraw undefined (type Wallet has no field or method Withdraw)

    Write the minimal amount of code for the test to run and check the failing test output

    1. func (w *Wallet) Withdraw(amount Bitcoin) {
    3. }

    wallet_test.go:33: got 20 BTC want 10 BTC

    Write enough code to make it pass

    1. func (w *Wallet) Withdraw(amount Bitcoin) {
    2.     w.balance -= amount
    3. }

    Refactor

    There’s some duplication in our tests, lets refactor that out.

    1. func TestWallet(t *testing.T) {
    3.     assertBalance := func(t *testing.T, wallet Wallet, want Bitcoin) {
    4.         t.Helper()
    5.         got := wallet.Balance()
    7.         if got != want {
    8.             t.Errorf("got %s want %s", got, want)
    9.         }
    10.     }
    12.     t.Run("Deposit", func(t *testing.T) {
    13.         wallet := Wallet{}
    14.         wallet.Deposit(Bitcoin(10))
    15.         assertBalance(t, wallet, Bitcoin(10))
    16.     })
    18.     t.Run("Withdraw", func(t *testing.T) {
    19.         wallet := Wallet{balance: Bitcoin(20)}
    20.         wallet.Withdraw(Bitcoin(10))
    21.         assertBalance(t, wallet, Bitcoin(10))
    22.     })
    24. }

    What should happen if you try to Withdraw more than is left in the account? For now, our requirement is to assume there is not an overdraft facility.

    How do we signal a problem when using Withdraw ?

    In Go, if you want to indicate an error it is idiomatic for your function to return an err for the caller to check and act on.

    Let’s try this out in a test.

    Write the test first

    We want Withdraw to return an error if you try to take out more than you have and the balance should stay the same.

    We then check an error has returned by failing the test if it is nil.

    nil is synonymous with null from other programming languages. Errors can be nil because the return type of Withdraw will be error, which is an interface. If you see a function that takes arguments or returns values that are interfaces, they can be nillable.

    Like null if you try to access a value that is nil it will throw a runtime panic. This is bad! You should make sure that you check for nils.

    Try and run the test

    ./wallet_test.go:31:25: wallet.Withdraw(Bitcoin(100)) used as value

    1. func (w *Wallet) Withdraw(amount Bitcoin) error {
    2.     w.balance -= amount
    3.     return nil
    4. }

    Again, it is very important to just write enough code to satisfy the compiler. We correct our Withdraw method to return error and for now we have to return something so let’s just return nil.

    Write enough code to make it pass

    1. func (w *Wallet) Withdraw(amount Bitcoin) error {
    3.     if amount > w.balance {
    4.         return errors.New("oh no")
    5.     }
    7.     w.balance -= amount
    8.     return nil
    9. }

    Remember to import errors into your code.

    errors.New creates a new error with a message of your choosing.

    Refactor

    Let’s make a quick test helper for our error check just to help our test read clearer

    2.     t.Helper()
    3.     if err == nil {
    4.         t.Error("wanted an error but didnt get one")
    5.     }
    6. }

    And in our test

    1. t.Run("Withdraw insufficient funds", func(t *testing.T) {
    2.     err := wallet.Withdraw(Bitcoin(100))
    4.     assertBalance(t, wallet, Bitcoin(20))
    5.     assertError(t, err)
    6. })

    Hopefully when returning an error of “oh no” you were thinking that we might iterate on that because it doesn’t seem that useful to return.

    Assuming that the error ultimately gets returned to the user, let’s update our test to assert on some kind of error message rather than just the existence of an error.

    Write the test first

    Update our helper for a string to compare against.

    1. assertError := func(t *testing.T, got error, want string) {
    2.     t.Helper()
    3.     if got == nil {
    4.         t.Fatal("didn't get an error but wanted one")
    5.     }
    7.     if got.Error() != want {
    8.         t.Errorf("got %q, want %q", got, want)
    9.     }
    10. }

    And then update the caller

    1. t.Run("Withdraw insufficient funds", func(t *testing.T) {
    2.     startingBalance := Bitcoin(20)
    3.     wallet := Wallet{startingBalance}
    4.     err := wallet.Withdraw(Bitcoin(100))
    6.     assertBalance(t, wallet, startingBalance)
    7.     assertError(t, err, "cannot withdraw, insufficient funds")
    8. })

    We’ve introduced t.Fatal which will stop the test if it is called. This is because we don’t want to make any more assertions on the error returned if there isn’t one around. Without this the test would carry on to the next step and panic because of a nil pointer.

    Try to run the test

    wallet_test.go:61: got err 'oh no' want 'cannot withdraw, insufficient funds'

    Write enough code to make it pass

    1. func (w *Wallet) Withdraw(amount Bitcoin) error {
    3.     if amount > w.balance {
    4.         return errors.New("cannot withdraw, insufficient funds")
    5.     }
    7.     w.balance -= amount
    8.     return nil
    9. }

    We have duplication of the error message in both the test code and the Withdraw code.

    It would be really annoying for the test to fail if someone wanted to re-word the error and it’s just too much detail for our test. We don’t really care what the exact wording is, just that some kind of meaningful error around withdrawing is returned given a certain condition.

    In Go, errors are values, so we can refactor it out into a variable and have a single source of truth for it.

    1. var ErrInsufficientFunds = errors.New("cannot withdraw, insufficient funds")
    3. func (w *Wallet) Withdraw(amount Bitcoin) error {
    5.     if amount > w.balance {
    6.         return ErrInsufficientFunds
    7.     }
    9.     w.balance -= amount
    10.     return nil
    11. }

    The var keyword allows us to define values global to the package.

    This is a positive change in itself because now our Withdraw function looks very clear.

    Next we can refactor our test code to use this value instead of specific strings.

    1. func TestWallet(t *testing.T) {
    3.     t.Run("Deposit", func(t *testing.T) {
    4.         wallet := Wallet{}
    5.         wallet.Deposit(Bitcoin(10))
    6.         assertBalance(t, wallet, Bitcoin(10))
    7.     })
    9.     t.Run("Withdraw with funds", func(t *testing.T) {
    10.         wallet := Wallet{Bitcoin(20)}
    11.         wallet.Withdraw(Bitcoin(10))
    12.         assertBalance(t, wallet, Bitcoin(10))
    13.     })
    15.     t.Run("Withdraw insufficient funds", func(t *testing.T) {
    16.         wallet := Wallet{Bitcoin(20)}
    17.         err := wallet.Withdraw(Bitcoin(100))
    19.         assertBalance(t, wallet, Bitcoin(20))
    20.         assertError(t, err, ErrInsufficientFunds)
    21.     })
    22. }
    24. func assertBalance(t *testing.T, wallet Wallet, want Bitcoin) {
    25.     t.Helper()
    26.     got := wallet.Balance()
    28.     if got != want {
    29.         t.Errorf("got %q want %q", got, want)
    30.     }
    31. }
    33. func assertError(t *testing.T, got error, want error) {
    34.     t.Helper()
    35.     if got == nil {
    36.         t.Fatal("didn't get an error but wanted one")
    37.     }
    39.     if got != want {
    40.         t.Errorf("got %q, want %q", got, want)
    41.     }
    42. }

    And now the test is easier to follow too.

    I have moved the helpers out of the main test function just so when someone opens up a file they can start reading our assertions first, rather than some helpers.

    Another useful property of tests is that they help us understand the real usage of our code so we can make sympathetic code. We can see here that a developer can simply call our code and do an equals check to ErrInsufficientFunds and act accordingly.

    Unchecked errors

    Whilst the Go compiler helps you a lot, sometimes there are things you can still miss and error handling can sometimes be tricky.

    There is one scenario we have not tested. To find it, run the following in a terminal to install errcheck, one of many linters available for Go.

    go get -u github.com/kisielk/errcheck

    Then, inside the directory with your code run errcheck .

    You should get something like

    wallet_test.go:17:18: wallet.Withdraw(Bitcoin(10))

    What this is telling us is that we have not checked the error being returned on that line of code. That line of code on my computer corresponds to our normal withdraw scenario because we have not checked that if the is successful that an error is not returned.

    Here is the final test code that accounts for this.

    Wrapping up

    • Go copies values when you pass them to functions/methods so if you’re writing a function that needs to mutate state you’ll need it to take a pointer to the thing you want to change.
    • The fact that Go takes a copy of values is useful a lot of the time but sometimes you wont want your system to make a copy of something, in which case you need to pass a reference. Examples could be very large data or perhaps things you intend only to have one instance of (like database connection pools).

    nil

    • Pointers can be nil
    • When a function returns a pointer to something, you need to make sure you check if it’s nil or you might raise a runtime exception, the compiler wont help you here.
    • Useful for when you want to describe a value that could be missing
    • Errors are the way to signify failure when calling a function/method.
    • By listening to our tests we concluded that checking for a string in an error would result in a flaky test. So we refactored to use a meaningful value instead and this resulted in easier to test code and concluded this would be easier for users of our API too.
    • This is not the end of the story with error handling, you can do more sophisticated things but this is just an intro. Later sections will cover more strategies.
    • Don’t just check errors, handle them gracefully

    Create new types from existing ones

    • Useful for adding more domain specific meaning to values

    Pointers and errors are a big part of writing Go that you need to get comfortable with. Thankfully the compiler will usually help you out if you do something wrong, just take your time and read the error.