From 8e475621c828cd9b9167f90407717af646c43663 Mon Sep 17 00:00:00 2001 From: Rob Pike Date: Mon, 9 Sep 2013 10:13:02 +1000 Subject: go.blog: update link in "first go program" There's an indicator to a "clever" trick, but the file changed underfoot. The for loop it was linked to didn't seem particularly clever. R=golang-dev, adg CC=golang-dev https://golang.org/cl/13518043 --- content/first-go-program.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/first-go-program.article b/content/first-go-program.article index e972ed1..3e31585 100644 --- a/content/first-go-program.article +++ b/content/first-go-program.article @@ -117,7 +117,7 @@ For instance, Rob called his method receivers `this`, but now we use shorter context-specific names. There are hundreds of more significant examples and to this day we're still discovering better ways to write Go code. (Check out the [[https://github.com/golang/glog][glog package]]'s clever trick for -[[https://github.com/golang/glog/blob/master/glog.go#L854][handling verbosity levels]].) +[[https://github.com/golang/glog/blob/c6f9652c7179652e2fd8ed7002330db089f4c9db/glog.go#L893][handling verbosity levels]].) I wonder what we'll learn tomorrow. -- cgit v1.2.3