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

package main

type T1	// ERROR "unexpected newline in type declaration"

type T2 /* // ERROR "unexpected EOF in type declaration" */
test: use testlib (final 61) 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/5671080 2012-02-16 21:51:04 -07:00			`// errorcheck`
gc: improved syntax errors * example-based syntax errors (go.errors) * enable bison's more specific errors and translate grammar token names into tokens like ++ * test cases R=ken2, r, ken3 CC=golang-dev https://golang.org/cl/194085 2010-01-27 00:13:22 -07:00
all: make copyright headers consistent with one space after period Follows suit with https://go-review.googlesource.com/#/c/20111. Generated by running $ grep -R 'Go Authors. All' * \| cut -d":" -f1 \| while read F;do perl -pi -e 's/Go Authors. All/Go Authors. All/g' $F;done The code in cmd/internal/unvendor wasn't changed. Fixes #15213 Change-Id: I4f235cee0a62ec435f9e8540a1ec08ae03b1a75f Reviewed-on: https://go-review.googlesource.com/21819 Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> 2016-04-10 15:32:26 -06:00			`// Copyright 2010 The Go Authors. All rights reserved.`
gc: improved syntax errors * example-based syntax errors (go.errors) * enable bison's more specific errors and translate grammar token names into tokens like ++ * test cases R=ken2, r, ken3 CC=golang-dev https://golang.org/cl/194085 2010-01-27 00:13:22 -07:00			`// Use of this source code is governed by a BSD-style`
			`// license that can be found in the LICENSE file.`

			`package main`

cmd/compile/internal/syntax: differentiate between ';' and '\n' in syntax errors Towards better syntax error messages: With this change, the parser knows whether a semicolon was an actual ';' in the source, or whether it was an automatically inserted semicolon as result of a '\n' or EOF. Using this information in error messages makes them more understandable. For #17328. Change-Id: I8cd9accee8681b62569d0ecef922d38682b401eb Reviewed-on: https://go-review.googlesource.com/36636 Reviewed-by: Matthew Dempsky <mdempsky@google.com> 2017-02-08 18:30:45 -07:00			`type T1 // ERROR "unexpected newline in type declaration"`

			`type T2 /* // ERROR "unexpected EOF in type declaration" */`