diff options
author | Rob Pike <r@golang.org> | 2014-10-01 15:25:56 -0700 |
---|---|---|
committer | Rob Pike <r@golang.org> | 2014-10-01 15:25:56 -0700 |
commit | 03ad4cafb641a61aac3bed5ee7aa3502e24424df (patch) | |
tree | 87956a3a8303096874209890401eb025d83f20d8 /doc | |
parent | 843bbf32df3423ca8ab59490f46412e48a36cabf (diff) | |
download | go-03ad4cafb641a61aac3bed5ee7aa3502e24424df.tar.gz |
doc/go_faq.html: explain the policy about unused imports a little better
This new text won't stop the whining but it might focus the whining a little more.
LGTM=adg
R=golang-codereviews, adg
CC=golang-codereviews
https://codereview.appspot.com/146680044
Diffstat (limited to 'doc')
-rw-r--r-- | doc/go_faq.html | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/go_faq.html b/doc/go_faq.html index 5813e1d04..ec3689aeb 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -1661,14 +1661,17 @@ Can I stop these complaints about my unused variable/import?</h3> <p> The presence of an unused variable may indicate a bug, while -unused imports just slow down compilation. -Accumulate enough unused imports in your code tree and -things can get very slow. -For these reasons, Go allows neither. +unused imports just slow down compilation, +an effect that can become substantial as a program accumulates +code and programmers over time. +For these reasons, Go refuses to compile programs with unused +variables or imports, +trading short-term convenience for long-term build speed and +program clarity. </p> <p> -When developing code, it's common to create these situations +Still, when developing code, it's common to create these situations temporarily and it can be annoying to have to edit them out before the program will compile. </p> |