Ian Lance Taylor schrieb am Dienstag, 25. August 2020 um 00:35:33 UTC+2: > I've seen objections that a language change for generics should not > implicitly pull in a change to non-generic code. That seems fair. It > may be the right thing to do, but it should be justified separately. > So we're going to start with "any" only being accepted as a type > constraint, and we can discuss making the name available for all uses > separately, probably on issue 33232. >
I understand the motivation, but I hope this artificial restriction is eventually lifted, because I find special cases and exceptions to generality make a language more confusing to learn ("Why can I use this here but not there, even though it's referring to the same thing?"). -- 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/2c13095f-ccce-43cc-9e52-f3ecd0bba733n%40googlegroups.com.