x/blog: add non-pointer note for errors.As example

Since this is a very high SEO article and it's a copy-pasteable block, it gets
copy pasted without much thought, which leads to problems when the error is a
concrete type / interface / etc.

This CL adds a small note that users should watch out for the case when the
error type is not a pointer.

Fixes golang/go#35361

Change-Id: Ibbd950c2a73a5f30cdab3517e042f69465adff97
Reviewed-on: https://go-review.googlesource.com/c/blog/+/252877
Reviewed-by: Jonathan Amsterdam <jba@google.com>
Reviewed-by: Kevin Burke <kev@inburke.com>
Trust: Jean de Klerk <deklerk@google.com>
Trust: Damien Neil <dneil@google.com>
1 file changed
tree: ed5ef928fb775d52d082ae72ce64fe4ed67c112d
  1. content/
  2. static/
  3. support/
  4. template/
  5. .gcloudignore
  6. .gitattributes
  7. app.yaml
  8. appengine.go
  10. blog.go
  11. codereview.cfg
  14. go.mod
  15. go.sum
  17. local.go
  18. local_test.go
  20. README.md
  21. rewrite.go

Go Blog

This repository holds the Go Blog server code and content.


The easiest way to install is to run go get -u golang.org/x/blog. You can also manually git clone the repository to $GOPATH/src/golang.org/x/blog.

Running Locally

To run the blog server locally:

go run . -reload

and then visit http://localhost:8080/ in your browser.


Articles are written in the x/tools/present format. Articles on the blog should have broad interest to the Go community, and are mainly written by Go contributors. We encourage you to share your experiences using Go on your own website, and to share them with the Go community. Hugo is a static site server written in Go that makes it easy to write and share your stories.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the blog is located at https://github.com/golang/go/issues. Prefix your issue with “x/blog:” in the subject line, so it is easy to find.


  1. To deploy blog.golang.org, run:

    GO111MODULE=on gcloud --project=golang-org app deploy --no-promote app.yaml

    This will create a new version, which can be viewed within the golang-org GCP project.

  2. Check that the deployed version looks OK (click the version link in GCP).

  3. If all is well, click “Migrate Traffic” to move 100% of the blog.golang.org traffic to the new version.

  4. You're done.