I don't see why it should be in the grammar. Just a regular type alias for
interface{} in the builtin scope, a regular predeclared identifier. It
wouldn't break anyone's code. If someone already has an 'any' type or
variable in their package their version shadows the builtin one, and they
can still use interface{} as a generic type constraint. At least that's how
it works with other builtin type aliases like 'rune':
https://play.golang.org/p/KRX3fIBV9qW
--
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/99559372-bcc5-4a12-aca1-6af1cf62931bn%40googlegroups.com.
