summaryrefslogtreecommitdiffhomepage
path: root/util/ringbuffer/ringbuffer.go
AgeCommit message (Collapse)AuthorFilesLines
2025-08-28util/ringbuffer: rename to ringlogJames Tucker1-79/+0
I need a ringbuffer in the more traditional sense, one that has a notion of item removal as well as tail loss on overrun. This implementation is really a clearable log window, and is used as such where it is used. Updates #cleanup Updates tailscale/corp#31762 Signed-off-by: James Tucker <james@tailscale.com>
2024-04-16all: use Go 1.22 range-over-intBrad Fitzpatrick1-1/+1
Updates #11058 Change-Id: I35e7ef9b90e83cac04ca93fd964ad00ed5b48430 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
2024-03-21wgengine/magicsock: don't use endpoint debug ringbuffer on mobile.Brad Fitzpatrick1-0/+7
Save some memory. Updates tailscale/corp#18514 Change-Id: Ibcaf3c6d8e5cc275c81f04141d0f176e2249509b Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
2023-02-21util/ringbuffer: move generic ringbuffer from corp repoAndrew Dunham1-0/+72
Also add some basic tests for this implementation. Signed-off-by: Andrew Dunham <andrew@du.nham.ca> Change-Id: I307ebb6db91d0c172657befb276b38ccb638f828