mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
go/types, types2: better error message for some invalid integer array lengths
Don't say "array length must be integer" if it is in fact an integer. Fixes #59209 Change-Id: If60b93a0418f5837ac334412d3838eec25eeb855 Reviewed-on: https://go-review.googlesource.com/c/go/+/479115 Reviewed-by: Robert Griesemer <gri@google.com> Run-TryBot: Robert Griesemer <gri@google.com> Reviewed-by: Robert Findley <rfindley@google.com> Auto-Submit: Robert Griesemer <gri@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
This commit is contained in:
parent
d49b11be1d
commit
bf9d9b7dba
7 changed files with 30 additions and 11 deletions
|
|
@ -13,7 +13,7 @@ var d ["abc"]int // ERROR "invalid array bound|not numeric|must be integer"
|
|||
var e [nil]int // ERROR "use of untyped nil|invalid array (bound|length)|not numeric|must be constant"
|
||||
// var f [e]int // ok with Go 1.17 because an error was reported for e; leads to an error for Go 1.18
|
||||
var f [ee]int // ERROR "undefined|undeclared"
|
||||
var g [1 << 65]int // ERROR "array bound is too large|overflows|must be integer"
|
||||
var g [1 << 65]int // ERROR "array bound is too large|overflows|invalid array length"
|
||||
var h [len(a)]int // ok
|
||||
|
||||
func ff() string
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue