content: fix confusing control flow in errors slide
The example showing error handling has the right shape,
but does not break after printing an error message, causing
the execution to continue with the happy-path case regardless
of whether or not there was an error.
Despite there not being any evident scope here, a return shows
what the idiomatic control flow would look like.
Fixes golang/go#12926
Change-Id: I54f8cfaf5d4bbc193089a320342272bfe2fe20f6
Reviewed-on: https://go-review.googlesource.com/15861
Reviewed-by: Andrew Gerrand <adg@golang.org>
diff --git a/content/methods.article b/content/methods.article
index 4792d8a..c2050fc 100644
--- a/content/methods.article
+++ b/content/methods.article
@@ -102,6 +102,7 @@
i, err := strconv.Atoi("42")
if err != nil {
fmt.Printf("couldn't convert number: %v\n", err)
+ return
}
fmt.Println("Converted integer:", i)
