I want to re-emphasize that all of these are micro-benchmarks. They say nothing useful at all, as proven by this thread; in some circumstances, the added cost may be significant, in others it isn't. The same rule that has been repeated lots of times on this list still applies: Write your program to be simple and readable, *if* it is too slow, benchmark and improve. Basing your code on what any of these Benchmarks says is just ridiculous, base it on the bottlenecks you measure in your actual, real-world program running on the actual production hardware with actual production data.
-- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
