This partially addresses the issue below: In many (all) cases we want to
handle invalid ... use in the parser as a syntax error; but this ensures
that we get a decent error if we get here anyway.
Updates #43680.
Change-Id: I93af43a5f5741d8bc76e7a13c0db75e6edf43111
Reviewed-on: https://go-review.googlesource.com/c/go/+/283475
Trust: Robert Griesemer <gri@golang.org>
Reviewed-by: Robert Findley <rfindley@google.com>
m1(T)
}
+// There is no such thing as a variadic generic type.
+type _[T ... /* ERROR invalid use of ... */ interface{}] struct{}
+
// Generic interfaces may be embedded as one would expect.
type I2 interface {
I1(int) // method!
check.ident(x, e, nil, false)
case *syntax.DotsType:
- // ellipses are handled explicitly where they are legal
+ // dots are handled explicitly where they are legal
// (array composite literals and parameter lists)
check.error(e, "invalid use of '...'")
goto Error
typ.elem = check.varType(e.Elem)
return typ
+ case *syntax.DotsType:
+ // dots are handled explicitly where they are legal
+ // (array composite literals and parameter lists)
+ check.error(e, "invalid use of '...'")
+ check.use(e.Elem)
+
case *syntax.StructType:
typ := new(Struct)
def.setUnderlying(typ)