mirror of https://github.com/golang/go.git
runtime: document that cleanups can run concurrently with each other
Fixes #71825. Change-Id: I25af19eb72d75f13cf661fc47ee5717782785326 Reviewed-on: https://go-review.googlesource.com/c/go/+/650696 Reviewed-by: Carlos Amedee <carlos@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Michael Pratt <mpratt@google.com>
This commit is contained in:
parent
76c7028253
commit
1421b982dc
|
|
@ -30,8 +30,10 @@ import (
|
|||
// unreachable at the same time, their cleanups all become eligible to run
|
||||
// and can run in any order. This is true even if the objects form a cycle.
|
||||
//
|
||||
// A single goroutine runs all cleanup calls for a program, sequentially. If a
|
||||
// cleanup function must run for a long time, it should create a new goroutine.
|
||||
// Cleanups run concurrently with any user-created goroutines.
|
||||
// Cleanups may also run concurrently with one another (unlike finalizers).
|
||||
// If a cleanup function must run for a long time, it should create a new goroutine
|
||||
// to avoid blocking the execution of other cleanups.
|
||||
//
|
||||
// If ptr has both a cleanup and a finalizer, the cleanup will only run once
|
||||
// it has been finalized and becomes unreachable without an associated finalizer.
|
||||
|
|
|
|||
Loading…
Reference in New Issue