1645
97%

Ran 14 Mar 2017 10:42PM UTC

Jobs 2

Files 36

Run time 1min

Badge

Embed ▾

pending completion

Build # 1645

Build Type

Pull #376

travis-ci

Committed by

web-flow

Commit Message

Expose Buffer pools to third-party encoders

Zap currently uses an internal package to house its buffer pool, and it returns
all buffers to that pool. This is problematic for two reasons:

1. First, third-party encoders can easily corrupt the pool by keeping a
   reference to a buffer.
2. Second, third-party encoders can't pool their buffers, since zap needs to
   know how to return them to their pools.

This PR introduces a `buffer.Pool` type to solve this problem. Individual
buffers can only be created via a pool, and each buffer keeps a reference to its
pool of origin. This allows zap to continue using a single internal pool, but it
allows third-party encoders to safely pool their buffers too.

Pull Request Pull Request #376: Expose Buffer pools to third-party encoders

Run Details

2231 of 2304 relevant lines covered (96.83%)

137775.91 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	1645.1	14 Mar 2017 10:42PM UTC	36	96.83	Travis Job 1645.1
2	1645.2	14 Mar 2017 10:43PM UTC	36	96.83	Travis Job 1645.2

Source Files on build 1645

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

uber-go / zap / 1645
97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1645

uber-go / zap / 1645 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 1645

uber-go / zap / 1645
97%

README BADGES
x