Personally I am happy with the current way of expressing constraints, i.e., interface-like + type lists, but I do think constraints and interfaces, are two different concepts, and forcing them into a same box does not mitigate the extra cognitive load needed to understand generics (which, as in the current draft proposal, is rather light).
On the other hand, I am not sure how to balance this against other factors (many of which I am not even aware of), like backward compatibility, so this is just my two cents. -- 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/66c8aa16-dc3a-44dd-8b6f-595992e4cf98o%40googlegroups.com.
