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

fmt: non-exported nil interfaces show up as "?reflect.Value?" on "%#v" #8843

Closed
niemeyer opened this issue Sep 30, 2014 · 3 comments
Closed

fmt: non-exported nil interfaces show up as "?reflect.Value?" on "%#v" #8843

niemeyer opened this issue Sep 30, 2014 · 3 comments
Milestone

Comments

@niemeyer
Copy link
Contributor

@niemeyer niemeyer commented Sep 30, 2014

This code:

    type T struct { v interface{} }
    fmt.Printf("%#v\n", T{})

outputs this:

    main.T{v:?reflect.Value?}
@niemeyer
Copy link
Contributor Author

@niemeyer niemeyer commented Sep 30, 2014

Comment 1:

Labels changed: added release-go1.4, repo-main.

@rsc
Copy link
Contributor

@rsc rsc commented Sep 30, 2014

Comment 2:

Status changed to Accepted.

@robpike
Copy link
Contributor

@robpike robpike commented Oct 1, 2014

Comment 3:

This issue was closed by revision 9f40842.

Status changed to Fixed.

@niemeyer niemeyer added fixed labels Oct 1, 2014
@rsc rsc added this to the Go1.4 milestone Apr 14, 2015
@rsc rsc removed the release-go1.4 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
wheatman added a commit to wheatman/go-akaros that referenced this issue Jun 25, 2018
This thing should never be called, but before
151960044 it was being called, incorrectly.
This is now just a precaution but let's pretend it
Fixes golang#8843
even though that was fixed by 151960044.
The test case was already there and ran, another mystery.

LGTM=rsc
R=rsc
CC=golang-codereviews
https://golang.org/cl/151970043
wheatman added a commit to wheatman/go-akaros that referenced this issue Jun 26, 2018
This thing should never be called, but before
151960044 it was being called, incorrectly.
This is now just a precaution but let's pretend it
Fixes golang#8843
even though that was fixed by 151960044.
The test case was already there and ran, another mystery.

LGTM=rsc
R=rsc
CC=golang-codereviews
https://golang.org/cl/151970043
wheatman added a commit to wheatman/go-akaros that referenced this issue Jul 9, 2018
This thing should never be called, but before
151960044 it was being called, incorrectly.
This is now just a precaution but let's pretend it
Fixes golang#8843
even though that was fixed by 151960044.
The test case was already there and ran, another mystery.

LGTM=rsc
R=rsc
CC=golang-codereviews
https://golang.org/cl/151970043
wheatman added a commit to wheatman/go-akaros that referenced this issue Jul 30, 2018
This thing should never be called, but before
151960044 it was being called, incorrectly.
This is now just a precaution but let's pretend it
Fixes golang#8843
even though that was fixed by 151960044.
The test case was already there and ran, another mystery.

LGTM=rsc
R=rsc
CC=golang-codereviews
https://golang.org/cl/151970043
This issue was closed.
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
You can’t perform that action at this time.