mirror of https://github.com/golang/go.git
The tree's pretty inconsistent about single space vs double space after a period in documentation. Make it consistently a single space, per earlier decisions. This means contributors won't be confused by misleading precedence. This CL doesn't use go/doc to parse. It only addresses // comments. It was generated with: $ perl -i -npe 's,^(\s*// .+[a-z]\.) +([A-Z]),$1 $2,' $(git grep -l -E '^\s*//(.+\.) +([A-Z])') $ go test go/doc -update Change-Id: Iccdb99c37c797ef1f804a94b22ba5ee4b500c4f7 Reviewed-on: https://go-review.googlesource.com/20022 Reviewed-by: Rob Pike <r@golang.org> Reviewed-by: Dave Day <djd@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> |
||
|---|---|---|
| .. | ||
| internal | ||
| README | ||
| doc.go | ||
| pprof.go | ||
README
The pprof in this directory is adapted from the pprof used inside Google for C++, Java, and Go programs. Because it was developed for that broader context, it is overgeneralized when used here for the specific use case of profiling standard Go programs. However, we've left the abstractions intact in order to share updates between this copy and Google's internal one. Please do not take the level of abstraction in this program as an example to follow in your own.