Jan Mercl schrieb am Dienstag, 18. August 2020 um 16:45:54 UTC+2: > I don't think so. The type list in this case is syntactically just an > identifier list, i.e not a list containing possibly eg. type > literals/anonymous types. >
I just looked into the draft design again: If composite types like slices and structs are allowed, as discussed in [1] and [2], then it is not just an identifier list. [1] Composite types in constraints <https://go.googlesource.com/proposal/+/refs/heads/master/design/go2draft-type-parameters.md#composite-types-in-constraints> type byteseq interface { type string, []byte } [2] Notes on composite types in type lists <https://go.googlesource.com/proposal/+/refs/heads/master/design/go2draft-type-parameters.md#notes-on-composite-types-in-type-lists> type structField interface { type struct { a int; x int }, struct { b int; x float64 }, struct { c int; x uint64 } } -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/48c0d6fb-16ce-4495-b520-d4a28166c122n%40googlegroups.com.
