mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
all: fix various doc comment formatting nits
A run of lines that are indented with any number of spaces or tabs format as a <pre> block. This commit fixes various doc comments that format badly according to that (standard) rule. For example, consider: // - List item. // Second line. // - Another item. Because the - lines are unindented, this is actually two paragraphs separated by a one-line <pre> block. This CL rewrites it to: // - List item. // Second line. // - Another item. Today, that will format as a single <pre> block. In a future release, we hope to format it as a bulleted list. Various other minor fixes as well, all in preparation for reformatting. For #51082. Change-Id: I95cf06040d4186830e571cd50148be3bf8daf189 Reviewed-on: https://go-review.googlesource.com/c/go/+/384257 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
This commit is contained in:
parent
df89f2ba53
commit
7d87ccc860
63 changed files with 619 additions and 606 deletions
|
|
@ -319,16 +319,16 @@ type arenaHint struct {
|
|||
// mSpanManual, or mSpanFree. Transitions between these states are
|
||||
// constrained as follows:
|
||||
//
|
||||
// * A span may transition from free to in-use or manual during any GC
|
||||
// phase.
|
||||
// * A span may transition from free to in-use or manual during any GC
|
||||
// phase.
|
||||
//
|
||||
// * During sweeping (gcphase == _GCoff), a span may transition from
|
||||
// in-use to free (as a result of sweeping) or manual to free (as a
|
||||
// result of stacks being freed).
|
||||
// * During sweeping (gcphase == _GCoff), a span may transition from
|
||||
// in-use to free (as a result of sweeping) or manual to free (as a
|
||||
// result of stacks being freed).
|
||||
//
|
||||
// * During GC (gcphase != _GCoff), a span *must not* transition from
|
||||
// manual or in-use to free. Because concurrent GC may read a pointer
|
||||
// and then look up its span, the span state must be monotonic.
|
||||
// * During GC (gcphase != _GCoff), a span *must not* transition from
|
||||
// manual or in-use to free. Because concurrent GC may read a pointer
|
||||
// and then look up its span, the span state must be monotonic.
|
||||
//
|
||||
// Setting mspan.state to mSpanInUse or mSpanManual must be done
|
||||
// atomically and only after all other span fields are valid.
|
||||
|
|
@ -1706,7 +1706,7 @@ func spanHasNoSpecials(s *mspan) {
|
|||
// offset & next, which this routine will fill in.
|
||||
// Returns true if the special was successfully added, false otherwise.
|
||||
// (The add will fail only if a record with the same p and s->kind
|
||||
// already exists.)
|
||||
// already exists.)
|
||||
func addspecial(p unsafe.Pointer, s *special) bool {
|
||||
span := spanOfHeap(uintptr(p))
|
||||
if span == nil {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue