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/go: show full syntax error list from go/parser #2811

Closed
rogpeppe opened this issue Jan 30, 2012 · 7 comments
Closed

cmd/go: show full syntax error list from go/parser #2811

rogpeppe opened this issue Jan 30, 2012 · 7 comments
Milestone

Comments

@rogpeppe
Copy link
Contributor

When one of the test files has a syntax error, I'd expect to see a few lines of error,
as we get when compiling non-test files.

Instead, only a single line of error is printed.
For example:

/home/rog/src/go/src/launchpad.net/goamz/ec2/ec2t_test.go:71:9: expected expression (and
120 more errors)
@rsc
Copy link
Contributor

rsc commented Jan 30, 2012

Comment 1:

It would also be nice to make the go/parser syntax errors
as nice as the ones that we get from the compiler.

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

Owner changed to builder@golang.org.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Jan 30, 2012

Comment 2:

Labels changed: added go1-must.

@rsc
Copy link
Contributor

rsc commented Jan 31, 2012

Comment 3:

This issue was closed by revision 42526e2.

Status changed to Fixed.

@rogpeppe
Copy link
Contributor Author

Comment 4:

I still see this issue.
96bd78e7d35e weekly/weekly.2012-02-22

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Feb 28, 2012

Comment 5:

Can you send a self-contained test case?

@rsc
Copy link
Contributor

rsc commented Feb 29, 2012

Comment 6:

Never mind, I found the culprit.

@rsc
Copy link
Contributor

rsc commented Mar 1, 2012

Comment 7:

This issue was closed by revision b03a5f6.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone 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

3 participants