On Wed, Mar 11, 2020 at 1:43 PM Nicola Murino <nicola.mur...@gmail.com> wrote:
> So I wrote a proof of concept allocator that tries to avoid all these > extra allocations reusing the previously allocated slices: > > https://github.com/drakkan/sftp/blob/master/allocator.go > > Any particular reason you avoided something like sync.Pool ? It could be useful in your case, allocation pattern depending. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAGrdgiU%2BpUA8NOW1xsMbAjMDX9XrAaePxuq-EJvwM1Hj48opVQ%40mail.gmail.com.
