Golang in sixty seconds — panic

We can use the panic function to cause a runtime error in Golang. This can be useful when paired with therecover function for error handling within our application. We may be tempted to use recover like this:

panic("AAAH!")
str := recover()
fmt.Println(str)

However we will never reach the line afterpanic as it will terminate the program. We therefore need to make use of thedeferstatement when using recover. This means that recover will always be called at the end of the function, even if there is a runtime error.

defer func() {
  str := recover()
  fmt.Println(str)
}
panic("AAAH!")

In this case we would seeAAAH! output to the terminal on reaching this part of our program.

panic should be used sparingly as it will terminate the program. Often it will be better to return an error instead of causing a panic. If you think that the problem you are anticipating should cause the program to crash, then use panic, otherwise create an error and return it instead.

Other stories about Golang:

Golang in sixty seconds - consuming JSON

Let's look at how you can consume JSON and turn it into a Go type

20 Jan 2022

Golang in sixty seconds - Pointers

A pointer is the location in memory where a value lives. It’s very important to understand pointers so I’ll give you a cheat sheet to help

03 Dec 2021

Golang in sixty seconds - return multiple values from functions

Golang allows you to return multiple values from a function and to name your return values

05 Aug 2022

Learn Golang with me

I'll take you through creating a simple pomodoro timer, explaining my decisions along the way.

05 Oct 2021

Golang in sixty seconds - folders and packages

How to structure your Golang code into folders

28 Jan 2022

I also write about:

FrontEnd

Testing

TypeScript

Working Practices

PostgreSQL