aboutsummaryrefslogtreecommitdiff
path: root/src/runtime/traceback.go
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2018-11-22 11:46:44 +0100
committerTobias Klauser <tobias.klauser@gmail.com>2018-12-02 15:12:26 +0000
commit9e277f7d554455e16ba3762541c53e9bfc1d8188 (patch)
treea72e026004116edc63d3171d5d4e612ad299c265 /src/runtime/traceback.go
parentb397248168fcb26400ac6afb88bf6080497a819e (diff)
downloadgo-9e277f7d554455e16ba3762541c53e9bfc1d8188.tar.gz
go-9e277f7d554455e16ba3762541c53e9bfc1d8188.zip
all: use "reports whether" consistently instead of "returns whether"
Follow-up for CL 147037 and after Brad noticed the "returns whether" pattern during the review of CL 150621. Go documentation style for boolean funcs is to say: // Foo reports whether ... func Foo() bool (rather than "returns whether") Created with: $ perl -i -npe 's/returns whether/reports whether/' $(git grep -l "returns whether" | grep -v vendor) Change-Id: I15fe9ff99180ad97750cd05a10eceafdb12dc0b4 Reviewed-on: https://go-review.googlesource.com/c/150918 Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Diffstat (limited to 'src/runtime/traceback.go')
-rw-r--r--src/runtime/traceback.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/runtime/traceback.go b/src/runtime/traceback.go
index 9d2f7f037c..0328fee4e6 100644
--- a/src/runtime/traceback.go
+++ b/src/runtime/traceback.go
@@ -876,7 +876,7 @@ func isExportedRuntime(name string) bool {
return len(name) > n && name[:n] == "runtime." && 'A' <= name[n] && name[n] <= 'Z'
}
-// elideWrapperCalling returns whether a wrapper function that called
+// elideWrapperCalling reports whether a wrapper function that called
// function "name" should be elided from stack traces.
func elideWrapperCalling(name string) bool {
// If the wrapper called a panic function instead of the