diff options
author | Martin Möhrmann <moehrmann@google.com> | 2020-04-29 12:23:32 +0200 |
---|---|---|
committer | Martin Möhrmann <moehrmann@google.com> | 2020-04-29 19:58:47 +0000 |
commit | f2163c4d458df70bd46f284f995419135f0e1fc3 (patch) | |
tree | 1b4f2e830b93f2f44df73581e89ad6f2efbca22d /src/bytes | |
parent | 35dce1d67c730a0f49c82660e94fe8305cac6861 (diff) | |
download | go-f2163c4d458df70bd46f284f995419135f0e1fc3.tar.gz go-f2163c4d458df70bd46f284f995419135f0e1fc3.zip |
bytes, strings: align requirements for functions passed to FieldFuncs
golang.org/cl/229763 removed the documentation of requirements of
the function passed to FieldsFunc. The current implementation does
not require functions to return consistent results but this had not
been the case for previous implementations.
Add the requirement for consistent results back to the documentation
to allow for future implementations to be more allocation efficient
for an output with more than 32 fields. This is possible with a two
pass algorithm first determining the number of fields used to allocate
the output slice and then splitting the input into fields.
While at it align the documentation of bytes.FieldsFunc with
strings.FieldFunc.
Fixes #38630
Change-Id: Iabbf9ca3dff0daa41f4ec930a21a3dd98e19f122
Reviewed-on: https://go-review.googlesource.com/c/go/+/230797
Run-TryBot: Martin Möhrmann <moehrmann@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Robert Griesemer <gri@golang.org>
Diffstat (limited to 'src/bytes')
-rw-r--r-- | src/bytes/bytes.go | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/bytes/bytes.go b/src/bytes/bytes.go index 0dce6af226..16d1854c44 100644 --- a/src/bytes/bytes.go +++ b/src/bytes/bytes.go @@ -445,8 +445,9 @@ func Fields(s []byte) [][]byte { // It splits the slice s at each run of code points c satisfying f(c) and // returns a slice of subslices of s. If all code points in s satisfy f(c), or // len(s) == 0, an empty slice is returned. -// FieldsFunc makes no guarantees about the order in which it calls f(c). -// If f does not return consistent results for a given c, FieldsFunc may crash. +// +// FieldsFunc makes no guarantees about the order in which it calls f(c) +// and assumes that f always returns the same value for a given c. func FieldsFunc(s []byte, f func(rune) bool) [][]byte { // A span is used to record a slice of s of the form s[start:end]. // The start index is inclusive and the end index is exclusive. |