aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlberto Donizetti <alb.donizetti@gmail.com>2019-06-01 15:28:19 +0200
committerAlberto Donizetti <alb.donizetti@gmail.com>2019-06-11 16:45:51 +0000
commit1f1f3d2b450bb9b46a281dc119148605afd67c6d (patch)
treec01a94446dd343f14f3aab9fb13e1d2ed2b8df1b
parentdb40fe78fefcfdeefb4ac4a94c72cfb20f40ee77 (diff)
downloadgolang-id-tour-1f1f3d2b450bb9b46a281dc119148605afd67c6d.tar.xz
tour: btrees do not store values just in leaves
The concurrency/7 slide (the binary tree exercise) says: > There can be many different binary trees with the same sequence of values stored at the leaves. Which is misleading: in the btree in the exercise, values are not stored just in the leaves, the internal nodes hold values too. Fixes golang/tour#774 Change-Id: I71af71ccf36ac8ad87dfe73b751b461890c3a7e0 Reviewed-on: https://go-review.googlesource.com/c/tour/+/179937 Reviewed-by: Andrew Bonventre <andybons@golang.org>
-rw-r--r--content/concurrency.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/concurrency.article b/content/concurrency.article
index b6bd509..35945b0 100644
--- a/content/concurrency.article
+++ b/content/concurrency.article
@@ -94,7 +94,7 @@ Use a `default` case to try a send or receive without blocking:
* Exercise: Equivalent Binary Trees
-There can be many different binary trees with the same sequence of values stored at the leaves. For example, here are two binary trees storing the sequence 1, 1, 2, 3, 5, 8, 13.
+There can be many different binary trees with the same sequence of values stored in it. For example, here are two binary trees storing the sequence 1, 1, 2, 3, 5, 8, 13.
.image /content/img/tree.png