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
..
syntax	regexp/syntax: update documentation for Parse.	2013-07-18 21:28:00 +02:00
testdata	regexp: move to old/regexp, replace with exp/regexp	2011-09-26 18:33:13 -04:00
all_test.go	regexp: fix index panic in Replace	2012-12-22 11:14:56 -05:00
example_test.go	regexp: add examples	2012-11-27 10:33:15 -05:00
exec2_test.go	regexp: exclude exhaustive RE2 test from running under race detector.	2013-07-19 23:44:22 +10:00
exec_test.go	regexp: use a very fast random generator for benchmarks.	2013-07-20 23:31:51 +02:00
exec.go	pkg: Add & fix Copyright of "hand generated" files	2012-01-19 10:14:56 -08:00
find_test.go	regexp: move to old/regexp, replace with exp/regexp	2011-09-26 18:33:13 -04:00
regexp.go	all: be more idiomatic when documenting boolean return values.	2013-07-23 11:59:49 +10:00