go/test/fixedbugs/bug169.go

// errorcheck

// Copyright 2009 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
var x = ''';		// ERROR "char|rune"
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-17 04:49:30 +00:00			`// errorcheck`
triple quote R=ken OCL=31868 CL=31874 2009-07-20 21:15:36 +00:00
			`// Copyright 2009 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`
cmd/compile/internal/syntax: better scanner error messages This is one of several changes that were part of a larger rewrite which I made in early 2019 after switching to the new number literal syntax implementation. The purpose of the rewrite was to simplify reading of source code (Unicode character by character) and speed up the scanner but was never submitted for review due to other priorities. Part 2 of 3: This change contains improvements to the scanner error messages: - Use "rune literal" rather than "character literal" to match the spec nomenclature. - Shorter, more to the point error messages. (For instance, "more than one character in rune literal" rather than "invalid character literal (more than one character)", etc.) Change-Id: I1aaf79003374a68dbb05926437ed305cf2a8ec96 Reviewed-on: https://go-review.googlesource.com/c/go/+/221602 Run-TryBot: Robert Griesemer <gri@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com> 2020-02-11 06:02:47 +00:00			`var x = '''; // ERROR "char\|rune"`
triple quote R=ken OCL=31868 CL=31874 2009-07-20 21:15:36 +00:00