go/test/blank1.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.

// Test that incorrect uses of the blank identifer are caught.
// Does not compile.

package _	// ERROR "invalid package name _"

func main() {
	_()	// ERROR "cannot use _ as value"
	x := _+1	// ERROR "cannot use _ as value"
	_ = x
}
test: use testlib (first 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, bradfitz CC=golang-dev https://golang.org/cl/5656082 2012-02-16 21:48:57 -07:00			`// errorcheck`
write-only variable _ R=ken OCL=34465 CL=34470 2009-09-09 00:16:19 -06: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.`

test: [a-c]: add introductory comments to tests Very few of the compiler regression tests include a comment saying waht they do. Many are obvious, some are anything but. I've started with a-c in the top directory. More will follow once we agree on the approach, correctness, and thoroughness here. zerodivide.go sneaked in too. R=rsc, r CC=golang-dev https://golang.org/cl/5656100 2012-02-18 19:19:43 -07:00			`// Test that incorrect uses of the blank identifer are caught.`
			`// Does not compile.`

write-only variable _ R=ken OCL=34465 CL=34470 2009-09-09 00:16:19 -06:00			`package _ // ERROR "invalid package name _"`

			`func main() {`
test: remove semiocolons. The ken directory is untouched so we have some examples with explicit semis. R=gri CC=golang-dev https://golang.org/cl/2157041 2010-09-03 18:36:13 -06:00			`_() // ERROR "cannot use _ as value"`
			`x := _+1 // ERROR "cannot use _ as value"`
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 12:50:45 -07:00			`_ = x`
write-only variable _ R=ken OCL=34465 CL=34470 2009-09-09 00:16:19 -06:00			`}`