wouldn't the compiler be able to use the fact that a return value is known not to be being used in a particular call, somewhere one or more of the returned values are assigned to a blank, to be able to generate faster code for that call?
or is it already being done? because, it seems to me, knowing if it was would effect how you might lay out a function and even promote some novel patterns. -- 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.
