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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

reflect: int-to-string conversion via Value.Convert incorrect for out-of-rune-bounds int values #42835

Closed
griesemer opened this issue Nov 25, 2020 · 1 comment
Closed

reflect: int-to-string conversion via Value.Convert incorrect for out-of-rune-bounds int values #42835

griesemer opened this issue Nov 25, 2020 · 1 comment
Labels
FrozenDueToAge release-blocker
Milestone
Go1.16

Comments

@griesemer
Copy link
Contributor

string(int) conversions via reflect.Value.Convert don't produce the same result as explicit string(int) conversions for out-of-rune-bounds integer arguments:

https://play.golang.org/p/BgUaHWE112o

This is a regression introduced by CL 220844 (6052838).

cc: @ianlancetaylor
@griesemer griesemer added this to the Go1.16 milestone Nov 25, 2020
@griesemer griesemer mentioned this issue Nov 25, 2020
Closed
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/273326 mentions this issue: reflect: fix Value.Convert for int-to-string conversions (regression)

@golang golang locked and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge release-blocker
Projects
None yet
Milestone
Go1.16
Development

No branches or pull requests
2 participants
@griesemer @gopherbot