You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output 1,2,3,4,... will only appear if we travers the tree in-order. Otherwise, the numbers might appear random. It would worth pointing that out in the description of the task.
The text was updated successfully, but these errors were encountered:
crisman
added a commit
to crisman/golang_website
that referenced
this issue
Feb 28, 2023
In "Exercise: Equivalent Binary Trees" neither the slide text nor the
code state Walk() should send the values in order. Doing so in order
makes using the output much more useful in Same(), but might not be easy
to see for readers that have not had a data structures class. In order
traversal is implied by reference with the binary tree being "always
sorted" and the output defined as "should be the numbers 1, 2, 3, ...,
10."
Update the slide text to say what Walk() does. Change Walk() comments in
code/solution to match.
Fixesgolang/tour#158
Context: https://tour.golang.org/concurrency/8
The output 1,2,3,4,... will only appear if we travers the tree in-order. Otherwise, the numbers might appear random. It would worth pointing that out in the description of the task.
The text was updated successfully, but these errors were encountered: