mirror of
https://github.com/golang/go
synced 2024-09-29 09:34:28 -06:00
dca0d03b9c
Don't skip closing parentheses of any kind after a missing expression. They are likely part of the lexical construct enclosing the expression. Fixes #33386. Change-Id: Ic0abc2037ec339a345ec357ccc724b7ad2a64c00 Reviewed-on: https://go-review.googlesource.com/c/go/+/188502 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
30 lines
752 B
Go
30 lines
752 B
Go
// errorcheck
|
|
|
|
// Copyright 2019 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.
|
|
|
|
// Verify that we don't get spurious follow-on errors
|
|
// after a missing expression. Specifically, the parser
|
|
// shouldn't skip over closing parentheses of any kind.
|
|
|
|
package p
|
|
|
|
func _() {
|
|
go func() { // no error here about goroutine
|
|
send <-
|
|
}() // ERROR "expecting expression"
|
|
}
|
|
|
|
func _() {
|
|
defer func() { // no error here about deferred function
|
|
1 +
|
|
}() // ERROR "expecting expression"
|
|
}
|
|
|
|
func _() {
|
|
_ = (1 +) // ERROR "expecting expression"
|
|
_ = a[2 +] // ERROR "expecting expression"
|
|
_ = []int{1, 2, 3 + } // ERROR "expecting expression"
|
|
}
|