go/test/fixedbugs/bug175.go

// errorcheck

// Copyright 2009 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

package main

func f() (int, bool) { return 0, true }

func main() {
	x, y := f(), 2;	// ERROR "multi"
	_, _ = x, y
}
test: use testlib (second 100) X ,s;^// \$G (\$D/)?\$F\.go $;// compile;g X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A $;// build;g X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A && \./\$A\.out $;// run;g X ,s;^// errchk \$G( -e)? (\$D/)?\$F\.go $;// errorcheck;g R=golang-dev CC=golang-dev https://golang.org/cl/5673078 2012-02-17 04:49:30 +00:00			`// errorcheck`
multiple return in := bug R=ken OCL=32253 CL=32253 2009-07-27 23:59:10 +00:00
			`// Copyright 2009 The Go Authors. All rights reserved.`
			`// Use of this source code is governed by a BSD-style`
			`// license that can be found in the LICENSE file.`

			`package main`

			`func f() (int, bool) { return 0, true }`

			`func main() {`
			`x, y := f(), 2; // ERROR "multi"`
test: explicitly use variables to avoid gccgo "not used" error I haven't looked at the source, but the gc compiler appears to omit "not used" errors when there is an error in the initializer. This is harder to do in gccgo, and frankly I think the "not used" error is still useful even if the initializer has a problem. This CL tweaks some tests to avoid the error, which is not the point of these tests in any case. R=golang-dev, r CC=golang-dev https://golang.org/cl/5561059 2012-01-22 19:50:45 +00:00			`_, _ = x, y`
multiple return in := bug R=ken OCL=32253 CL=32253 2009-07-27 23:59:10 +00:00			`}`