mirror of
https://github.com/golang/go
synced 2024-11-23 16:50:06 -07:00
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/+/185099 Reviewed-by: Ian Lance Taylor <iant@golang.org> Reviewed-by: Rob Pike <r@golang.org>
This commit is contained in:
parent
9d56dd8ea3
commit
80cca23b59
@ -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 {
|
||||||
|
Loading…
Reference in New Issue
Block a user