Commit 80cca23b authored by Francesco Renzi's avatar Francesco Renzi Committed by Rob Pike

strings: document that order of pairs matters in NewReplacer

Update NewReplacer documentation to specify that in the case of
multiple matches at the same position, the matching old/new
pair that appears first in NewReplacer arguments takes precedence.

Fixes #32699

Change-Id: I9d0616d28e5cd8c9bfa301be201f2b0ebf361dff
Reviewed-on: https://go-review.googlesource.com/c/go/+/185099Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
Reviewed-by: default avatarRob Pike <r@golang.org>
parent 9d56dd8e
...@@ -25,7 +25,8 @@ type replacer interface { ...@@ -25,7 +25,8 @@ type replacer interface {
// NewReplacer returns a new Replacer from a list of old, new string // NewReplacer returns a new Replacer from a list of old, new string
// pairs. Replacements are performed in the order they appear in the // pairs. Replacements are performed in the order they appear in the
// target string, without overlapping matches. // target string, without overlapping matches. The old string
// comparisons are done in argument order.
// //
// NewReplacer panics if given an odd number of arguments. // NewReplacer panics if given an odd number of arguments.
func NewReplacer(oldnew ...string) *Replacer { func NewReplacer(oldnew ...string) *Replacer {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment