On Thursday, January 26, 2017 at 8:08:28 PM UTC+8, Volker Dobler wrote: > > [...] Fewer select-block usages means more efficient code. >> > > What if the priority-enabled-select is much complexer and > massively less efficient than two all-equal-selects? > It might be less lines of code but not in itself more efficient > (for whatever definition of efficiency). > > V. >
This shouldn't happen. There is a case sorting stage in the select implementation. For priority-enabled-select, the sorting stage can be omitted, which makes the select flow a little more efficient (than the random sorting one) . -- 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.
