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

cmd/api: cannot analyse exported constants referring to unexported ones. #2906

Closed
remyoudompheng opened this issue Feb 7, 2012 · 3 comments
Milestone

Comments

@remyoudompheng
Copy link
Contributor

What steps will reproduce the problem?
1. add a package test with

package test

const a = 1
const A = a

2. run "go tool api test"

What is the expected output? What do you see instead?

Expected:
pkg test, const A ideal-int

Got:
2012/02/07 21:41:42 unknown kind in const "A" (*ast.Ident): can't resolve
existing constant "a"

The gccgo syscall package uses such things:

const O_APPEND = _O_APPEND
@bradfitz
Copy link
Contributor

bradfitz commented Feb 8, 2012

Comment 1:

http://golang.org/cl/5644050

Labels changed: added priority-go1, removed priority-triage.

Owner changed to @bradfitz.

Status changed to Started.

@bradfitz
Copy link
Contributor

bradfitz commented Feb 9, 2012

Comment 2:

Remy, feel like reviewing that patch?

@bradfitz
Copy link
Contributor

bradfitz commented Feb 9, 2012

Comment 3:

This issue was closed by revision c15a42e.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@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.
Projects
None yet
Development

No branches or pull requests

4 participants