But then you have path dependence, branching issues.. and add on top
multiple threads and caches... You mentioned it is not safe, well it is not
safe at all.
Seems to me that the combination of escape analysis + concurrent/parallel
GC is a better approach and is way safer.

And in the meanwhile, as the posts above indicated, you can avoid
allocating, avoid large datastructures of pointers etc. The sync/pool
package is quite handy to recycle your data structures and if you
preallocate, you also avoid heap fragmentation.
On Tuesday, November 25, 2014 8:18:33 AM UTC, Jason E. Aten wrote:

On Mon, Nov 24, 2014 at 9:09 PM, Tahir <welcometot...@gmail.com
<javascript:>> wrote:
If the GC has to recheck anyway what's the point of hints ?
Read the description of FREE_INSTANTLY. There's no recheck in this case.
The point of recheck under CHECK_FREE is to allow you to verify that your
hints are correct, before running at full speed under FREE_INSTANTLY.
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 | 22 of 32 | next ›
Discussion Overview
groupgolang-nuts @
postedNov 24, '14 at 4:39p
activeNov 26, '14 at 4:35a



site design / logo © 2022 Grokbase