We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
wiki: redirect everything to go.dev/wiki For #61940.
Adds clarity on how deleting elements from a slice can cause a memory leak thanks to the underlying array
added reference to golang.org/x/exp/slices
Add "Extend Capacity"
Clarify Expand and Extend
fix godoc.org / pkg.go.dev links
Revert f6920aaaf866d0e331b12fad4ee530079113b97f...75c3834c6757470db4b2507a742a18df4206efb6 on SliceTricks
It maybe a typo
I think there should be a colon ' : '
Updated SliceTricks (markdown)
tipo
Fix moveToFront and its headline
remove stray code in Insert section
remove append based slice copy patterns that are slower since go1.15 than make+copy
Revert e5998399c87e9f2de47e5108df584283db3c7fbd...46fe561befe97672f770640f831a9a545c77e540 on SliceTricks
batch slice cap should be actions divided by batchSize and plus one for remainder (added braces for clarity)
Add a sliding window function as shared here: https://gophers.slack.com/archives/C02A8LZKT/p1588980407253800
Ordered delete's check for `i<len(a)-1` is unnecessary. Slicing an n-length array using `[n:]` will return an empty array, and so the copy will do nothing.
once memory allocation for batches
Revert d28c2eed0adc1a35d49bd3446ec51646c3fd547a...7c1079779440dc52877765bc0a548c24a8ea0cbc on SliceTricks
fix: correct boundary checking for deleting an element