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: SetValue is ill-defined #1212

Closed
dsymonds opened this issue Oct 19, 2010 · 3 comments
Closed

reflect: SetValue is ill-defined #1212

dsymonds opened this issue Oct 19, 2010 · 3 comments
Labels
FrozenDueToAge

Comments

@dsymonds
Copy link
Contributor 

c.f. http://groups.google.com/group/golang-dev/browse_thread/thread/607a1d64c09432a7

I propose that the SetValue methods should mimic the "assignability"
requirements (to permit them, if not necessarily to enforce them).
@adg
Copy link
Contributor

adg commented Oct 19, 2010

Comment 1:

Status changed to Thinking.

@gopherbot
Copy link
Contributor

Comment 2 by Mickey.Killianey:

In addition to having a method for assignability, consider this a request for another
method that does conversion.
And ideally, some way of detecting whether or not assignment/conversion is legal between
two reflect.Types *before* you attempt the assignment/conversion.

@rsc
Copy link
Contributor

rsc commented Apr 20, 2011

Comment 3:

This issue was closed by revision e1ee3b5.

Status changed to Fixed.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dsymonds @rsc @adg @gopherbot