FAQ
The only way around it is to not use dynamic dispatch in any way, making sure the full code path is known to the compiler at run time. Clearly this doesn't scale to full programs, but you might be able to salvage some performance by doing what you can for a few hot spots.

Also, note that past a certain threshold large slices will be allocated on the heap no matter what.

--
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

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 4 | next ›
Discussion Overview
groupgolang-nuts @
categoriesgo
postedNov 6, '14 at 5:17p
activeNov 9, '14 at 11:23p
posts4
users4
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase