diff options
| author | Caleb Spare <cespare@gmail.com> | 2016-02-16 12:54:04 -0800 |
|---|---|---|
| committer | Andrew Gerrand <adg@golang.org> | 2016-02-16 21:29:04 +0000 |
| commit | 269f87ce4308f36b06088905c9cd0f8e9b563400 (patch) | |
| tree | ea59548c2074717bdf270e69c76fb58ffcee0cff /content/slices.article | |
| parent | f53436163e88b6c048dcf6e248f0ec87a0008e32 (diff) | |
content: fix typo and add forward blog post reference
Change-Id: Id6eeddc79a55095af68ee5b452119ea488b12870
Reviewed-on: https://go-review.googlesource.com/19517
Reviewed-by: Andrew Gerrand <adg@golang.org>
Diffstat (limited to 'content/slices.article')
| -rw-r--r-- | content/slices.article | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/content/slices.article b/content/slices.article index 998d4ae..f21cafd 100644 --- a/content/slices.article +++ b/content/slices.article @@ -99,7 +99,7 @@ Inside a function we could use the short declaration form, What exactly is this slice variable? It's not quite the full story, but for now think of a slice as a little data structure with two elements: a length and a pointer to an element -of a array. +of an array. You can think of it as being built like this behind the scenes: type sliceHeader struct { @@ -548,7 +548,9 @@ A historical note: The earliest implementation of strings always allocated, but were added to the language, they provided a model for efficient string handling. Some of the benchmarks saw huge speedups as a result. -There's much more to strings, of course, but they are a topic for another post. +There's much more to strings, of course, and the +[[http://blog.golang.org/strings][Strings, bytes, runes and characters in Go]] blog post +covers them in greater depth. * Conclusion |