diff options
| author | Tackx <tack@vxn.dev> | 2026-03-04 16:05:02 +0000 |
|---|---|---|
| committer | Gopher Robot <gobot@golang.org> | 2026-03-04 10:19:27 -0800 |
| commit | 2fe8435f08306e8eb19ca91cc4b03ab9f9655cef (patch) | |
| tree | 34bdfa9cba017b8819c30004d5f17742c98e962b /_content | |
| parent | 0a6e7586b8bdf0f38d9de3a08dd3c7d3d029577a (diff) | |
| download | go-x-website-2fe8435f08306e8eb19ca91cc4b03ab9f9655cef.tar.xz | |
_content/blog/allocation-optimizations: fix typo
Fix a typo I noticed while reading the article.
Change-Id: I0e7159922cd60aafd0de498914eb8a60fd58a87a
GitHub-Last-Rev: b0a080fcc2c0b47a3597310098d2d50315476bda
GitHub-Pull-Request: golang/website#347
Reviewed-on: https://go-review.googlesource.com/c/website/+/750020
Reviewed-by: Keith Randall <khr@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Keith Randall <khr@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Diffstat (limited to '_content')
| -rw-r--r-- | _content/blog/allocation-optimizations.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/_content/blog/allocation-optimizations.md b/_content/blog/allocation-optimizations.md index d69e4ced..130d3305 100644 --- a/_content/blog/allocation-optimizations.md +++ b/_content/blog/allocation-optimizations.md @@ -276,7 +276,7 @@ the heap copy. This ensures that for our original `extract` code, if the number of items fits in our small stack-allocated buffer, we perform exactly 1 allocation of exactly the right size. If the number of items exceeds -the capacity our small stack-allocated buffer, we do our normal +the capacity of our small stack-allocated buffer, we do our normal doubling-allocation once the stack-allocated buffer overflows. The optimization that Go 1.26 does is actually better than the |