Rob Pike abe384f68a all: be more idiomatic when documenting boolean return values. ... Phrases like "returns whether or not the image is opaque" could be describing what the function does (it always returns, regardless of the opacity) or what it returns (a boolean indicating the opacity). Even when the "or not" is missing, the phrasing is bizarre. Go with "reports whether", which is still clunky but at least makes it clear we're talking about the return value. These were edited by hand. A few were cleaned up in other ways. R=golang-dev, dsymonds CC=golang-dev https://golang.org/cl/11699043		2013-07-23 11:59:49 +10:00
..
doc.go	fmt: change evalutation of indexed arg to match docs	2013-05-29 11:29:29 -04:00
export_test.go	fmt, log: stop using unicode	2012-03-06 23:27:11 -05:00
fmt_test.go	fmt: change evalutation of indexed arg to match docs	2013-05-29 11:29:29 -04:00
format.go	fmt: Remove dead code and make comments and variables consistent.	2013-01-22 17:12:45 -05:00
print.go	all: be more idiomatic when documenting boolean return values.	2013-07-23 11:59:49 +10:00
scan_test.go	fmt: Remove dead code and make comments and variables consistent.	2013-01-22 17:12:45 -05:00
scan.go	all: excise some warts found by vet -shadow	2013-06-20 16:14:40 -07:00
stringer_test.go	delete float, complex - code changes	2011-01-19 23:09:00 -05:00