Interesting work. I understand this is very much a work in progress; how would you (eventually) see the implementation of map(), e.g.:
https://play.golang.org/p/GogrfKf-oA Or is this an accepted limitation of functionality for simplicity, that any single generic scope must have at most a single generic type? Do you forsee any confusion or complexity in overloading "*" further (currently, pointers & math, eventually pointers & math & generics)? --- SER -- 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. For more options, visit https://groups.google.com/d/optout.
