Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/zapcore/field_test.go |
FileSize | 6752 |
MD5 | 273CE6DF31500ACBD1FE92C65EF7AE9B |
SHA-1 | 00DB8BB62783E4FF84BE60C8781D2F618702228D |
SHA-256 | B611D6560522CECBA07D780521ED00A36F8D477F41BAD2D94BE3FF70AD056471 |
SSDEEP | 96:RIwwQHNobEIqkCwUqVd39yHEqBe+Gy/E50Tv3rBpp9BvrPVdptcRoZcif0ZliFLy:HwQHNUTJh9YlnKwfYU4 |
TLSH | T194D16405EA398D5D3250D0C0093DAECE673CE0B688647AF5F46D435EB28E97C94A637D |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 76060 |
MD5 | EFFFAEEC48A0D2285F976F0710E15381 |
PackageDescription | Blazing fast, structured, leveled logging in Go. Package zap provides fast, structured, leveled logging. . For applications that log in the hot path, reflection-based serialization and string formatting are prohibitively expensive, they're CPU-intensive and make many small allocations. Put differently, using json.Marshal and fmt.Fprintf to log tons of interface{} makes your application slow. . Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | golang-go.uber-zap-dev |
PackageSection | devel |
PackageVersion | 1.7.1+git20171031.f85c78b-5 |
SHA-1 | 381771E7ACDEDF88DD8F9CF918FC3C27FD104607 |
SHA-256 | 29FD57F04A49C0AD7CF09F3A37FDDCBC3E12FB1C6C268994DA905DA97B228AD5 |