4 Commits

Author	SHA1	Message	Date
Robert Griesemer	7a1aa7dfaf	[dev.typeparams] test: adjust more test cases to match compiler -G output ... With this CL, the first ~500 errorcheck tests pass when running go run run.go -v -G in the $GOROOT/test directory (the log output includes a few dozen tests that are currently skipped). Change-Id: I9eaa2319fb39a090df54f8699ddc29ffe58b1bf1 Reviewed-on: https://go-review.googlesource.com/c/go/+/274975 Trust: Robert Griesemer <gri@golang.org> Run-TryBot: Robert Griesemer <gri@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com>	2020-12-03 17:55:56 +00:00
Russ Cox	2b1c9b4be2	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-16 23:49:30 -05:00
Ian Lance Taylor	387e7c2742	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 11:50:45 -08:00
Russ Cox	a587d9a73f	multiple return in := bug ... R=ken OCL=32253 CL=32253	2009-07-27 16:59:10 -07:00