What version of Go are you using (go version)?
Git 46ab7a5
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
linux/ppc64le, but that seems inapplicable to this issue.
What did you do?
Read the source for generate_cert.go, saw what looks like a superfluous return.
|
if err != nil { |
|
log.Fatalf("Failed to open key.pem for writing: %v", err) |
|
return |
|
} |
What did you expect to see?
if err != nil {
log.Fatalf("Failed to open key.pem for writing: %v", err)
}
No return, since log.Fatalf makes it unnecessary, just like in the rest of the file.
What did you see instead?
if err != nil {
log.Fatalf("Failed to open key.pem for writing: %v", err)
return
}
The return seems unnecessary, and doesn't match the style in the rest of the file when log.Fatalf is used.
What version of Go are you using (
go version)?Git 46ab7a5
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env)?linux/ppc64le, but that seems inapplicable to this issue.
What did you do?
Read the source for
generate_cert.go, saw what looks like a superfluousreturn.go/src/crypto/tls/generate_cert.go
Lines 157 to 160 in 46ab7a5
What did you expect to see?
No return, since
log.Fatalfmakes it unnecessary, just like in the rest of the file.What did you see instead?
The
returnseems unnecessary, and doesn't match the style in the rest of the file whenlog.Fatalfis used.