On Thu, Dec 31, 2020 at 9:45 PM da...@suarezhouse.net <da...@suarezhouse.net> wrote:
> Real use cases have been provided it appears for both why generics can be > good and how they can be used negligently (love the sextuple example BTW). Some future language will invent the idea that you should be able to create anonymous product types on the fly and use those as return values when you want multiple return values. They'll even realize once you have anonymous product types, every function just needs to take a single argument and return a single argument, since you can just use an anonymous product type (i.e., a tuple) if you want to pass multiple things. People will even realize that when you compile this, you don't have to pass a pointer to said tuple but can make a choice on calling convention which passes such tuples in registers to speed up the system and be as fast as any other language. Then people will have reinvented Standard ML from 1991. -- 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/CAGrdgiVJe_2L5QZ13v-SBZq2C7_e6nX8JDCAE23BcpWqGyH99Q%40mail.gmail.com.
