Go Optimizations 101, Go Details & Tips 101 and Go Generics 101 are all updated for Go 1.25 now. The most cost-effective way to get them is through this book bundle in the Leanpub book store.

defer 2

What does the following program print?

package main

func bar() (r int) {
	defer func() {
		r += 4
		if recover() != nil {
			r += 8
		}
	}()
	
	var f func()
	defer f()
	f = func() {
		r += 2
	}

	return 1
}

func main() {
	println(bar())
}

Choices:

Answer: 13

Run it on Go play.

Key points:
  • Line 12: when the call f() is pushed to the defer call queue, f is evaluated as nil. Calling a nil function produces a panic. But the panic doesn't happen at the push time. Instead, it will panic at the execution time later during the exiting phase of the bar() call.
  • Line 13-15: the assignment to f has not any impacts on the execution effect. In other words, this assignment is actually a no-op.
  • Line 4-9: a defer call could modify the named return result of its containing function (here the bar function).


(more articles ↡)

The Go 101 project is hosted on Github. Welcome to improve Go 101 articles by submitting corrections for all kinds of mistakes, such as typos, grammar errors, wording inaccuracies, description flaws, code bugs and broken links.

If you would like to learn some Go details and facts every serveral days, please follow Go 101's official Twitter account @zigo_101.

Tapir, the author of Go 101, has been on writing the Go 101 series books and maintaining the go101.org website since 2016 July. New contents will be continually added to the book and the website from time to time. Tapir is also an indie game developer. You can also support Go 101 by playing Tapir's games (made for both Android and iPhone/iPad):
Individual donations via PayPal are also welcome.

Articles in this book:

(more are coming ...)