I don't see how this fixes issue 177 On Tue, Jul 22, 2014 at 11:47 ...
10 years, 7 months ago
(2014-07-22 01:50:25 UTC)
#2
I don't see how this fixes issue 177
On Tue, Jul 22, 2014 at 11:47 AM, <adg@golang.org> wrote:
> Reviewers: golang-codereviews,
>
> Message:
> Hello golang-codereviews@googlegroups.com,
>
> I'd like you to review this change to
> https://code.google.com/p/go-tour
>
>
> Description:
> go-tour: fix bad printf call
>
> Fixes issue 177.
>
> Please review this at https://codereview.appspot.com/116080044/
>
> Affected files (+2, -2 lines):
> M solutions/webcrawler.go
>
>
> Index: solutions/webcrawler.go
> ===================================================================
> --- a/solutions/webcrawler.go
> +++ b/solutions/webcrawler.go
> @@ -67,8 +67,8 @@
> done <- true
> }(u)
> }
> - for i := range urls {
> - fmt.Printf("<- [%v] %v/%v Waiting for child %v.\n", url,
> i, len(urls))
> + for i, u := range urls {
> + fmt.Printf("<- [%v] %v/%v Waiting for child %v.\n", url,
> i, len(urls), u)
> <-done
> }
> fmt.Printf("<- Done with %v\n", url)
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-codereviews" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-codereviews+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
Issue 116080044: code review 116080044: go-tour: fix bad printf call
(Closed)
Created 10 years, 7 months ago by adg
Modified 10 years, 7 months ago
Reviewers:
Base URL:
Comments: 0