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: can't type check gcc61264.go #9474

Closed
bradfitz opened this issue Dec 30, 2014 · 2 comments
Closed

go/types: can't type check gcc61264.go #9474

bradfitz opened this issue Dec 30, 2014 · 2 comments
Assignees
Milestone

Comments

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Dec 30, 2014

The tools repo is failing its tests right now with:

...
ok      golang.org/x/tools/go/loader    13.698s
ok      golang.org/x/tools/go/pointer   50.195s
ok      golang.org/x/tools/go/ssa   31.041s
ok      golang.org/x/tools/go/ssa/interp    29.511s
ok      golang.org/x/tools/go/ssa/ssautil   0.044s
--- FAIL: TestStdFixed (1.03s)
    stdlib_test.go:112: /linux-amd64-nocgo-7e56eeeced89/go/test/fixedbugs/gcc61264.go:12:9: expected statement, found 'map' (and 1 more errors)
FAIL
FAIL    golang.org/x/tools/go/types 2.469s
ok      golang.org/x/tools/go/types/typeutil    0.021s
ok      golang.org/x/tools/go/vcs   0.177s
ok      golang.org/x/tools/godoc    0.121s
?       golang.org/x/tools/godoc/analysis   [no test files]

Where go/test/fixedbugs/gcc61264.go is:

package main

func main() {
        map[int]int{}[0]++
}
@bradfitz bradfitz added this to the Go1.5 milestone Dec 30, 2014
@alandonovan
Copy link
Contributor

@alandonovan alandonovan commented Dec 30, 2014

That looks like a parse error. Will investigate...

Loading

@griesemer
Copy link
Contributor

@griesemer griesemer commented Dec 30, 2014

This is definitively a parse error. The code is syntactically valid.

Loading

@golang golang locked and limited conversation to collaborators Jun 25, 2016
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