1
0
mirror of https://github.com/golang/go synced 2024-11-23 13:50:06 -07:00
go/test/fixedbugs/issue32133.go
Robert Griesemer 5411953df5 cmd/compile: avoid follow-on errors for literals with syntax errors
- only convert literal strings if there were no syntax errors
  (some of the conversion routines exit if there is an error)
- mark nodes for literals with syntax errors to avoid follow-on
  errors
- don't attempt to import packages whose path had syntax errors

Fixes #32133.

Change-Id: I1803ad48c65abfecf6f48ddff1e27eded5e282c5
Reviewed-on: https://go-review.googlesource.com/c/go/+/192437
Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2019-08-29 23:37:07 +00:00

43 lines
694 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.
package p
// errors for the //line-adjusted code below
// ERROR "newline in string"
// ERROR "newline in character literal"
// ERROR "newline in string"
// ERROR "string not terminated"
//line :10:1
import "foo
//line :19:1
func _() {
0x // ERROR "hexadecimal literal has no digits"
}
func _() {
0x1.0 // ERROR "hexadecimal mantissa requires a 'p' exponent"
}
func _() {
0_i // ERROR "'_' must separate successive digits"
}
func _() {
//line :11:1
'
}
func _() {
//line :12:1
"
}
func _() {
//line :13:1
`