Skip to content

cmd/gc: bad file/line number <epoch> #5028

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

Closed
bradfitz opened this issue Mar 11, 2013 · 3 comments
Closed

cmd/gc: bad file/line number <epoch> #5028

bradfitz opened this issue Mar 11, 2013 · 3 comments

Comments

@bradfitz
Copy link
Contributor

Bad error message.  Both lines are weird.

$ cat x.go
package main

func main() {
        f := func(n int) string {
                for n >= 0 {
                        return "x"
                }
        }
        _ = f
}

$ go build x.go
# command-line-arguments
<epoch>: missing return at end of function
@rsc
Copy link
Contributor

rsc commented Mar 12, 2013

Comment 1:

[The time for maybe has passed.]

Labels changed: removed go1.1maybe.

@rogpeppe
Copy link
Contributor

Comment 2:

a marginally simpler case:
% cat x.go
package main
func main() {
    _ = func() error {}
}
% go tool 6g x.go
<epoch>: missing return at end of function
%

@rsc
Copy link
Contributor

rsc commented Mar 25, 2013

@bradfitz bradfitz added the fixed label Mar 25, 2013
@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