From: Agniva De Sarker <agnivade@yahoo.co.in>
Date: Mon, 14 Jan 2019 08:13:11 +0000 (+0530)
Subject: bufio: fix emptyFinalToken example to handle multiple Reads
X-Git-Tag: go1.13beta1~1251
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=5126feadd6e4ca890da0156c59b159085959120e;p=gostls13.git

bufio: fix emptyFinalToken example to handle multiple Reads

Fixes #25909

Change-Id: I9a53a1a06aab5d1877a8e9b1b8b782d77d6027a8
Reviewed-on: https://go-review.googlesource.com/c/157758
Reviewed-by: Bryan C. Mills <bcmills@google.com>
Run-TryBot: Bryan C. Mills <bcmills@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
---

diff --git a/src/bufio/example_test.go b/src/bufio/example_test.go
index 4666e6d985..bb57139918 100644
--- a/src/bufio/example_test.go
+++ b/src/bufio/example_test.go
@@ -94,6 +94,9 @@ func ExampleScanner_emptyFinalToken() {
 				return i + 1, data[:i], nil
 			}
 		}
+		if !atEOF {
+			return 0, nil, nil
+		}
 		// There is one final token to be delivered, which may be the empty string.
 		// Returning bufio.ErrFinalToken here tells Scan there are no more tokens after this
 		// but does not trigger an error to be returned from Scan itself.