Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/website: go1.20 docs refer to strings.Clone as new #58234

Closed
benpbrown opened this issue Feb 2, 2023 · 3 comments
Closed

x/website: go1.20 docs refer to strings.Clone as new #58234

benpbrown opened this issue Feb 2, 2023 · 3 comments
Assignees
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done. website
Milestone

Comments

@benpbrown
Copy link

What did you do?

Visited https://go.dev/doc/go1.20

What did you expect to see?

No reference to strings.Clone as being new. I believe it was introduced in Go 1.18 for strings (https://go.dev/doc/go1.18) (but in 1.20 for bytes 馃檪 )

What did you see instead?

The following reference to a new function: The new [Clone](https://go.dev/pkg/strings/#Clone) function allocates a copy of a string.

@mknyszek mknyszek modified the milestones: Go1.21, Unreleased Feb 2, 2023
@mknyszek mknyszek changed the title doc: go1.20 docs refer to strings.Clone as new x/website: go1.20 docs refer to strings.Clone as new Feb 2, 2023
@mknyszek mknyszek added the NeedsFix The path to resolution is known, but the work has not been done. label Feb 2, 2023
@mknyszek
Copy link
Contributor

mknyszek commented Feb 2, 2023

Ah, that's probably a copy-paste error, looking at the rest of the content of each section.

@mknyszek
Copy link
Contributor

mknyszek commented Feb 2, 2023

I'll send out a CL.

@mknyszek mknyszek self-assigned this Feb 2, 2023
@gopherbot
Copy link

Change https://go.dev/cl/464775 mentions this issue: _content/doc: remove strings.Clone from Go 1.20 release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation NeedsFix The path to resolution is known, but the work has not been done. website
Projects
None yet
Development

No branches or pull requests

4 participants