How does this compare to sync.Pool?

[xeoncross]

sync.Pool seems to offer the same features so I'm wondering what differences exist between these projects.

[elithrar]

sync.Pool automatically GC's objects, which may not be what you want.

I wrote a short piece on the differences: http://blog.questionable.services/article/using-buffer-pools-with-go/#postscript

There are also a number of issues about sync.Pool that describe its limitations:

• proposal: sync: add function to free objects removed from a Pool golang/go#23216
• sync: Pool example suggests incorrect usage golang/go#23199
• proposal: add Reset field to sync.Pool to reset item before putting it back to the pool golang/go#18638

[xeoncross]

Thank you, these links were very helpful. Perhaps you should add them to the readme.

The automatic garbage collection of sync.Pool seems like it would kind of defeat the purpose of having a pool to prevent GC. I'll have to study it more.