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

go/types: make AssignableTo work for tuples #7692

Closed
griesemer opened this issue Apr 2, 2014 · 2 comments
Closed

go/types: make AssignableTo work for tuples #7692

griesemer opened this issue Apr 2, 2014 · 2 comments

Comments

@griesemer
Copy link
Contributor

@griesemer griesemer commented Apr 2, 2014

This is feature request, not a bug.

By adonovan:

"Assignable(tuple, tuple) should probably implement element-wise assignability
since that's the effective semantics when you return a multi-valued expression or
value,ok expression.    It comes up in my refactoring tool, I want to ask: can I assign
this expr (multi-valued) to this Signature.Result()?  It would be convenient if it
worked for tuples.  Not a big deal though."

(personal e-mail from 4/1/2014)

(This may be useful to do, especially if it would simplify checking of return
statements, etc. and cases where the lhs is multi-valued, and the rhs is a (single)
tuple).
@griesemer griesemer self-assigned this Apr 2, 2014
@bradfitz bradfitz removed the new label Dec 18, 2014
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc rsc removed the release-none label Apr 10, 2015
@rsc rsc changed the title go.tools/go.types: make AssignableTo work for tuples x/tools/go.types: make AssignableTo work for tuples Apr 14, 2015
@rsc rsc added this to the Unreleased milestone Apr 14, 2015
@rsc rsc removed this from the Unplanned milestone Apr 14, 2015
@rsc rsc removed the repo-tools label Apr 14, 2015
@griesemer griesemer changed the title x/tools/go.types: make AssignableTo work for tuples go/types: make AssignableTo work for tuples Jul 31, 2015
@griesemer
Copy link
Contributor Author

@griesemer griesemer commented Feb 25, 2017

Re-evaluate and make decision for 1.9.

Loading

@griesemer griesemer added this to the Go1.9 milestone Feb 25, 2017
@griesemer griesemer removed this from the Unreleased milestone Feb 25, 2017
@griesemer griesemer added this to the Unplanned milestone Mar 13, 2017
@griesemer griesemer removed this from the Go1.9 milestone Mar 13, 2017
@griesemer
Copy link
Contributor Author

@griesemer griesemer commented Dec 20, 2017

I'm going to close this for now. @alandonovan, if you still think this is important to have, please re-open, mark for Go 1.11 and "early-in-cycle". Thanks.

Loading

@griesemer griesemer closed this Dec 20, 2017
@golang golang locked and limited conversation to collaborators Dec 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants