[go] test: fix malformed string and casing in slices.go typeparam test
Gerrit Bot (Gerrit)
Gerrit Bot has uploaded the change for review![]( "Open in Gerrit")
Commit message
test: fix malformed string and casing in slices.go typeparam test
This change corrects a malformed string in TestEqual where a closing
parenthesis was missing. It also updates the panic messages in the
slices typeparam test to start with lowercase letters, aligning with
the Go project's style guidelines.
Change diff
diff --git a/test/typeparam/slices.go b/test/typeparam/slices.go
index b24817d..699d8ec 100644
--- a/test/typeparam/slices.go
+++ b/test/typeparam/slices.go
@@ -158,30 +158,30 @@
func TestEqual() {
s1 := []int{1, 2, 3}
if !_Equal(s1, s1) {
- panic(fmt.Sprintf("_Equal(%v, %v) = false, want true", s1, s1))
+ panic(fmt.Sprintf("_equal(%v, %v) = false, want true", s1, s1))
}
s2 := []int{1, 2, 3}
if !_Equal(s1, s2) {
- panic(fmt.Sprintf("_Equal(%v, %v) = false, want true", s1, s2))
+ panic(fmt.Sprintf("_equal(%v, %v) = false, want true", s1, s2))
}
s2 = append(s2, 4)
if _Equal(s1, s2) {
- panic(fmt.Sprintf("_Equal(%v, %v) = true, want false", s1, s2))
+ panic(fmt.Sprintf("_equal(%v, %v) = true, want false", s1, s2))
}
s3 := []float64{1, 2, math.NaN()}
if !_Equal(s3, s3) {
- panic(fmt.Sprintf("_Equal(%v, %v) = false, want true", s3, s3))
+ panic(fmt.Sprintf("_equal(%v, %v) = false, want true", s3, s3))
}
if _Equal(s1, nil) {
- panic(fmt.Sprintf("_Equal(%v, nil) = true, want false", s1))
+ panic(fmt.Sprintf("_equal(%v, nil) = true, want false", s1))
}
if _Equal(nil, s1) {
- panic(fmt.Sprintf("_Equal(nil, %v) = true, want false", s1))
+ panic(fmt.Sprintf("_equal(nil, %v) = true, want false", s1))
}
if !_Equal(s1[:0], nil) {
- panic(fmt.Sprintf("_Equal(%v, nil = false, want true", s1[:0]))
+ panic(fmt.Sprintf("_equal(%v, nil) = false, want true", s1[:0]))
}
}
@@ -193,20 +193,20 @@
s1 := []int{1, 2, 3}
s2 := []int{2, 3, 4}
if _EqualFn(s1, s1, offByOne[int]) {
- panic(fmt.Sprintf("_EqualFn(%v, %v, offByOne) = true, want false", s1, s1))
+ panic(fmt.Sprintf("_equalFn(%v, %v, offByOne) = true, want false", s1, s1))
}
if !_EqualFn(s1, s2, offByOne[int]) {
- panic(fmt.Sprintf("_EqualFn(%v, %v, offByOne) = false, want true", s1, s2))
+ panic(fmt.Sprintf("_equalFn(%v, %v, offByOne) = false, want true", s1, s2))
}
if !_EqualFn(s1[:0], nil, offByOne[int]) {
- panic(fmt.Sprintf("_EqualFn(%v, nil, offByOne) = false, want true", s1[:0]))
+ panic(fmt.Sprintf("_equalFn(%v, nil, offByOne) = false, want true", s1[:0]))
}
s3 := []string{"a", "b", "c"}
s4 := []string{"A", "B", "C"}
if !_EqualFn(s3, s4, strings.EqualFold) {
- panic(fmt.Sprintf("_EqualFn(%v, %v, strings.EqualFold) = false, want true", s3, s4))
+ panic(fmt.Sprintf("_equalFn(%v, %v, strings.EqualFold) = false, want true", s3, s4))
}
}
@@ -214,18 +214,18 @@
s1 := []int{1, 2, 3}
s2 := _Map(s1, func(i int) float64 { return float64(i) * 2.5 })
if want := []float64{2.5, 5, 7.5}; !_Equal(s2, want) {
- panic(fmt.Sprintf("_Map(%v, ...) = %v, want %v", s1, s2, want))
+ panic(fmt.Sprintf("_map(%v, ...) = %v, want %v", s1, s2, want))
}
s3 := []string{"Hello", "World"}
s4 := _Map(s3, strings.ToLower)
if want := []string{"hello", "world"}; !_Equal(s4, want) {
- panic(fmt.Sprintf("_Map(%v, strings.ToLower) = %v, want %v", s3, s4, want))
+ panic(fmt.Sprintf("_map(%v, strings.ToLower) = %v, want %v", s3, s4, want))
}
s5 := _Map(nil, func(i int) int { return i })
if len(s5) != 0 {
- panic(fmt.Sprintf("_Map(nil, identity) = %v, want empty slice", s5))
+ panic(fmt.Sprintf("_map(nil, identity) = %v, want empty slice", s5))
}
}
@@ -298,7 +298,7 @@
s1 := []int{1, 2, 3}
s2 := []int{4, 5}
if got := _Copy(s1, s2); got != 2 {
- panic(fmt.Sprintf("_Copy returned %d, want 2", got))
+ panic(fmt.Sprintf("_copy returned %d, want 2", got))
}
want := []int{4, 5, 3}
if !_Equal(s1, want) {
Change information
- M test/typeparam/slices.go
Related details
Code-Review
No-Unresolved-Comments
Review-Enforcement
TryBots-Pass
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Gopher Robot (Gerrit)
Gopher Robot added 1 comment![]( "Open in Gerrit")
I spotted some possible problems with your PR:
1. You usually need to reference a bug number for all but trivial or cosmetic fixes. For this repo, the format is usually 'Fixes #12345' or 'Updates #12345' at the end of the commit message. Should you have a bug reference?
Please address any problems by updating the GitHub PR.
When complete, mark this comment as 'Done' and click the [blue 'Reply' button](https://go.dev/wiki/GerritBot#i-left-a-reply-to-a-comment-in-gerrit-but-no-one-but-me-can-see-it) above. These findings are based on heuristics; if a finding does not apply, briefly reply here saying so.
To update the commit title or commit message body shown here in Gerrit, you must edit the GitHub PR title and PR description (the first comment) in the GitHub web interface using the 'Edit' button or 'Edit' menu entry there. Note: pushing a new commit to the PR will not automatically update the commit message used by Gerrit.
For more details, see:
- [how to update commit messages](https://go.dev/wiki/GerritBot/#how-does-gerritbot-determine-the-final-commit-message) for PRs imported into Gerrit.
- the Go project's [conventions for commit messages](https://go.dev/doc/contribute#commit_messages) that you should follow.
(In general for Gerrit code reviews, the change author is expected to [log in to Gerrit](https://go-review.googlesource.com/login/) with a Gmail or other Google account and then close out each piece of feedback by marking it as 'Done' if implemented as suggested or otherwise reply to each review comment. See the [Review](https://go.dev/doc/contribute#review) section of the Contributing Guide for details.)
Related details
Code-Review
No-Unresolved-Comments
Review-Enforcement
TryBots-Pass
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Jorge Pinto (Gerrit)
Jorge Pinto added 1 comment![]( "Open in Gerrit")
I spotted some possible problems with your PR:
1. You usually need to reference a bug number for all but trivial or cosmetic fixes. For this repo, the format is usually 'Fixes #12345' or 'Updates #12345' at the end of the commit message. Should you have a bug reference?Please address any problems by updating the GitHub PR.
When complete, mark this comment as 'Done' and click the [blue 'Reply' button](https://go.dev/wiki/GerritBot#i-left-a-reply-to-a-comment-in-gerrit-but-no-one-but-me-can-see-it) above. These findings are based on heuristics; if a finding does not apply, briefly reply here saying so.
To update the commit title or commit message body shown here in Gerrit, you must edit the GitHub PR title and PR description (the first comment) in the GitHub web interface using the 'Edit' button or 'Edit' menu entry there. Note: pushing a new commit to the PR will not automatically update the commit message used by Gerrit.
For more details, see:
- [how to update commit messages](https://go.dev/wiki/GerritBot/#how-does-gerritbot-determine-the-final-commit-message) for PRs imported into Gerrit.
- the Go project's [conventions for commit messages](https://go.dev/doc/contribute#commit_messages) that you should follow.
(In general for Gerrit code reviews, the change author is expected to [log in to Gerrit](https://go-review.googlesource.com/login/) with a Gmail or other Google account and then close out each piece of feedback by marking it as 'Done' if implemented as suggested or otherwise reply to each review comment. See the [Review](https://go.dev/doc/contribute#review) section of the Contributing Guide for details.)
Done
Related details
Code-Review
No-Unresolved-Comments
Review-Enforcement
TryBots-Pass
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |