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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reflect: do not deprecate Value.{Pointer,UnsafeAddr} #49187

Closed
cuonglm opened this issue Oct 27, 2021 · 1 comment
Closed

reflect: do not deprecate Value.{Pointer,UnsafeAddr} #49187

cuonglm opened this issue Oct 27, 2021 · 1 comment
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@cuonglm
Copy link
Member

cuonglm commented Oct 27, 2021

Coming here from #48665, we need to undeprecate Value.Pointer() and Value.UnsafeAddr().

@cuonglm cuonglm added the NeedsFix The path to resolution is known, but the work has not been done. label Oct 27, 2021
@cuonglm cuonglm added this to the Go1.18 milestone Oct 27, 2021
@cuonglm cuonglm self-assigned this Oct 27, 2021
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/359194 mentions this issue: reflect: undeprecate Value.{Pointer,UnsafeAddr}

@rsc rsc unassigned cuonglm Jun 23, 2022
@golang golang locked and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

2 participants