The more I think about it the less I understand why type list should reside
inside interfaces. I can only think of two reasons:
1) Avoid a new keyword for type lists.
2) The idea that only interfaces should be able to act as constraints.
Regarding 2): Why this artificial limitation? Why not allow all types as
constraints? Even int. It's nonsensical, but it would be like "interface{
type int }" in the current draft, which is nonsensical, too. The rule would
be simple: Any type can act both as normal type and as constraint. With the
possible exception of `anyof`s, until there is a solution to use them as
regular types as well.
--
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/8711bcf9-6ebe-4014-9034-d0a642078791n%40googlegroups.com.
