From dba2faf2c60bd3bf249641c7f09af2cbc984f645 Mon Sep 17 00:00:00 2001 From: Rob Pike Date: Wed, 1 Oct 2014 15:25:56 -0700 Subject: [PATCH] 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://golang.org/cl/146680044 --- doc/go_faq.html | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/go_faq.html b/doc/go_faq.html index 5813e1d047..ec3689aeb0 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?

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.

-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.

-- 2.48.1