- 23 Jan, 2019 3 commits
-
-
Steven Allen authored
Enable tests
-
Anton Petrov authored
-
Anton Petrov authored
-
- 09 Oct, 2018 1 commit
-
-
Steven Allen authored
-
- 06 Oct, 2018 2 commits
-
-
Steven Allen authored
pool pointers to pointers
-
Steven Allen authored
So, creating interfaces *allocates*. That means `pool.Put([]byte)` allocates, that's obviously bad. This was, unfortunately, showing up in go-ipfs after switching to a pool-backed yamux. What's the solution to too many allocations? More object pools!
-
- 04 Oct, 2018 3 commits
-
-
Steven Allen authored
-
Steven Allen authored
Fix overflow on 32-bit platforms.
-
Kevin Atkinson authored
-
- 21 Jan, 2018 8 commits
-
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
They won't use the buffer pool but it doesn't hurt to be nice to the user by allocating such slices anyways.
-
- 20 Dec, 2017 5 commits
-
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
-
Steven Allen authored
Before, this library assumed that we wanted to use pools for things other than byte slices. In practice, this isn't the case and supporting such use-cases made this library annoying to use.
-
Steven Allen authored
-
- 21 Nov, 2017 1 commit
-
-
Steven Allen authored
This way, copying it won't copy the underlying pool. Also, initialize it immediately instead of in an `init` function to ensure that it's fully initialized immediately.
-
- 19 Nov, 2017 1 commit
-
-
Steven Allen authored
This has moved to libp2p
-
- 17 Nov, 2017 3 commits
-
-
Steven Allen authored
Per the documentation, this example *isn't* guaranteed to work (and, in practice, it fails occasionally).
-
Steven Allen authored
-
Steven Allen authored
1. They're small. 2. We can avoid the lock (major speedup). 3. Better memory locality. 4. Much simpler.
-
- 13 Dec, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 06 Dec, 2014 1 commit
-
-
Juan Batiz-Benet authored
-