From 747ae2594e531eeef12cf276085f6409cb10ff2d Mon Sep 17 00:00:00 2001 From: Dmitri Shuralyov Date: Sun, 8 Nov 2015 19:14:07 -0800 Subject: [PATCH] go/buildutil: Fix example code for TagsFlag. The example incorrectly used buildutil.TagsDoc identifier which does not exist. It should be buildutil.TagsFlagDoc instead. The issue was introduced in https://golang.org/cl/9172 when this code was first written. Also use more idiomatic style for Go comments, '//' followed by a space, then tab (instead of skipping the space). Although both render correctly in godoc, this form is more correct and consistent. Change-Id: I3b3c9767fe313106a8ff81e7887f3241c5806b59 Reviewed-on: https://go-review.googlesource.com/16743 Reviewed-by: Alan Donovan --- go/buildutil/tags.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/go/buildutil/tags.go b/go/buildutil/tags.go index 97350940ea..525ecb6c5f 100644 --- a/go/buildutil/tags.go +++ b/go/buildutil/tags.go @@ -16,7 +16,7 @@ const TagsFlagDoc = "a list of `build tags` to consider satisfied during the bui // See $GOROOT/src/cmd/go/doc.go for description of 'go build -tags' flag. // // Example: -// flag.Var((*buildutil.TagsFlag)(&build.Default.BuildTags), "tags", buildutil.TagsDoc) +// flag.Var((*buildutil.TagsFlag)(&build.Default.BuildTags), "tags", buildutil.TagsFlagDoc) type TagsFlag []string func (v *TagsFlag) Set(s string) error {