mirror of
https://github.com/golang/go
synced 2024-11-25 01:08:02 -07:00
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
This commit is contained in:
parent
41914c1df8
commit
387e7c2742
@ -9,4 +9,5 @@ package _ // ERROR "invalid package name _"
|
||||
func main() {
|
||||
_() // ERROR "cannot use _ as value"
|
||||
x := _+1 // ERROR "cannot use _ as value"
|
||||
_ = x
|
||||
}
|
||||
|
@ -11,4 +11,5 @@ func main() {
|
||||
var c01 uint8 = '\07'; // ERROR "oct|char"
|
||||
var cx0 uint8 = '\x0'; // ERROR "hex|char"
|
||||
var cx1 uint8 = '\x'; // ERROR "hex|char"
|
||||
_, _, _, _ = c00, c01, cx0, cx1
|
||||
}
|
||||
|
@ -7,4 +7,5 @@
|
||||
package main
|
||||
func f() {
|
||||
v := 1 << 1025; // ERROR "overflow|stupid shift"
|
||||
_ = v
|
||||
}
|
||||
|
@ -10,5 +10,5 @@ func f() (int, bool) { return 0, true }
|
||||
|
||||
func main() {
|
||||
x, y := f(), 2; // ERROR "multi"
|
||||
_, _ = x, y
|
||||
}
|
||||
|
||||
|
@ -17,5 +17,5 @@ func main() {
|
||||
println(b)
|
||||
|
||||
var c int64 = (1<<i) + 4.0 // ok - it's all int64
|
||||
println(b)
|
||||
println(c)
|
||||
}
|
||||
|
@ -11,4 +11,5 @@ var notmain func()
|
||||
func main() {
|
||||
var x = &main // ERROR "address of|invalid"
|
||||
main = notmain // ERROR "assign to|invalid"
|
||||
_ = x
|
||||
}
|
||||
|
@ -65,4 +65,5 @@ func f() {
|
||||
cap(b2)+ // ERROR "illegal|invalid|must be"
|
||||
cap(b3)+
|
||||
cap(b4) // ERROR "illegal|invalid|must be"
|
||||
_ = x
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user