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
cmd/godoc: some consts are not well represented #5397
Labels
Milestone
Comments
Labels changed: added priority-later, godoc, removed priority-triage. Owner changed to @griesemer. Status changed to Accepted. |
Issue #7815 has been merged into this issue. |
CL https://golang.org/cl/144110044 mentions this issue. |
This issue was closed by revision 2b59c9d. Status changed to Fixed. |
josharian
added a commit
to josharian/go
that referenced
this issue
Dec 23, 2014
When constants were declared using unexported constants, the type information was lost when those constants were filtered out. This CL propagates the type information of unexported constants so that it is available for display. This is a follow-up to CL 144110044, which fixed this problem specifically for _ constants. Updates golang#5397. Change-Id: I3f0c767a4007d88169a5634ab2870deea4e6a740
josharian
added a commit
to josharian/go
that referenced
this issue
Dec 30, 2014
When constants were declared using unexported constants, the type information was lost when those constants were filtered out. This CL propagates the type information of unexported constants so that it is available for display. This is a follow-up to CL 144110044, which fixed this problem specifically for _ constants. Updates golang#5397. Change-Id: I3f0c767a4007d88169a5634ab2870deea4e6a740
josharian
added a commit
that referenced
this issue
Jan 6, 2015
When constants were declared using unexported constants, the type information was lost when those constants were filtered out. This CL propagates the type information of unexported constants so that it is available for display. This is a follow-up to CL 144110044, which fixed this problem specifically for _ constants. Updates #5397. Change-Id: I3f0c767a4007d88169a5634ab2870deea4e6a740 Reviewed-on: https://go-review.googlesource.com/2091 Reviewed-by: Robert Griesemer <gri@golang.org>
josharian
added a commit
to josharian/go
that referenced
this issue
Jan 6, 2015
When constants were declared using unexported constants, the type information was lost when those constants were filtered out. This CL propagates the type information of unexported constants so that it is available for display. This is a follow-up to CL 144110044, which fixed this problem specifically for _ constants. Updates golang#5397. Change-Id: I3f0c767a4007d88169a5634ab2870deea4e6a740
josharian
added a commit
that referenced
this issue
Feb 4, 2015
golang.org/cl/144110044 made _ consts treated as exported as a small, safe fix for #5397. It also introduced issue #9615. golang.org/cl/2091 then fixed the underlying issue, which was missing type information when the type was specified only for _. This cl reverts the original fix. Fixes #9615. Change-Id: I4815ad8292bb5bec18beb8c131b48949d9af8876 Reviewed-on: https://go-review.googlesource.com/3832 Reviewed-by: Robert Griesemer <gri@golang.org>
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jun 25, 2018
Fixes golang#5397. LGTM=adg R=gri, adg CC=golang-codereviews, rsc https://golang.org/cl/144110044
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jul 9, 2018
Fixes golang#5397. LGTM=adg R=gri, adg CC=golang-codereviews, rsc https://golang.org/cl/144110044
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jul 30, 2018
Fixes golang#5397. LGTM=adg R=gri, adg CC=golang-codereviews, rsc https://golang.org/cl/144110044
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: