Checking to see if err==nil is a very cheap operation. I think it is only a check to see if a word is equal to 0 but it definitely is at most checking two words. I'd like to see an implementation of what you suggest that is cheaper than that.

Note also that Go doesn't really do JIT optimization like some other languages do, so this is sort of out of the realm of things Go aims to do. At least as of now.

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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 4 of 10 | next ›
Discussion Overview
groupgolang-nuts @
postedFeb 4, '15 at 12:08a
activeFeb 4, '15 at 8:53p



site design / logo © 2022 Grokbase