1
97%
master: 97%

Ran 14 Mar 2017 11:12PM UTC

Files 36

Run time 2s

Badge

Embed ▾

Committed 14 Mar 2017 11:08PM UTC coverage: 97.004% (+0.2%) from 96.826%

Job # 1648.1

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

Expose Buffer pools to third-party encoders (#376)

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.

Coverage Stats

2234 of 2303 relevant lines covered (97.0%)

66516.7 hits per line

uber-go / zap / 1648 / 1
97%
master: 97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1648.1

uber-go / zap / 1648 / 1 97% master: 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1648.1

uber-go / zap / 1648 / 1
97%
master: 97%

README BADGES
x