container/ring.Ring.Next
standard libraryThe 9463rd most-called standard-library method by production calls. Called 67 times across 21 modules; 63 of those run outside tests and generated code.
- prod calls
- 63
- non-test, non-generated
- all calls
- 67
- total callsites
- modules
- 21
- distinct callers
- in loop
- 40%
- of prod calls
- in tests
- 6%
- 4 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Concrete method100%A method on a value whose type is known exactly.
who calls this
Notable callers
Production calls into Ring.Next from notable Go projects. Open one on the map to see what else it hammers.
where it's called
Callsites in the wild
12 representative callsites of 67, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
- in loop
- in loop
-
OpenDiablo2/OpenDiablo2 @v0.0.0-20211021131836-7f92c571bf04
in loop - in loop
- in loop
-
golang/go @v0.0.0-20260805010601-5d7583fe1f94
in loop - in loop
- in loop
- in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-handler/device-manager/mediated_devices_types.go:176
in loop - in loop
top callers
The modules that reach for it
The modules that call Ring.Next most in this snapshot.
- github.com/gogf/gf/v21116%
- github.com/gogf/gf1015%
- github.com/blevesearch/bleve69%
- github.com/hashicorp/consul57%
- github.com/lesnuages/snitch46%