mirror of
https://github.com/golang/go
synced 2024-11-24 07:00:13 -07:00
3c22e5ca27
Starting the error message with "expecting" rather than "missing" causes the syntax error mechanism to add additional helpful info (it recognizes "expecting" but not "missing"). Fixes #17328. Change-Id: I8482ca5e5a6a6b22e0ed0d831b7328e264156334 Reviewed-on: https://go-review.googlesource.com/36637 Run-TryBot: Robert Griesemer <gri@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
18 lines
592 B
Go
18 lines
592 B
Go
// errorcheck
|
|
|
|
// Copyright 2010 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.
|
|
|
|
// TODO(mdempsky): Update error expectations for new parser.
|
|
// The new parser emits an extra "missing { after for clause" error.
|
|
// The old parser is supposed to emit this too, but it panics first
|
|
// due to a nil pointer dereference.
|
|
|
|
package main
|
|
|
|
func main() {
|
|
for x // GCCGO_ERROR "undefined"
|
|
{ // ERROR "expecting .*{.* after for clause|missing operand"
|
|
z // ERROR "undefined|expecting { after for clause"
|