Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/field.go |
FileSize | 10824 |
MD5 | 60EB334E523717CA0461994D86520B51 |
SHA-1 | 064B5C0BECED56D72D724D614FBC67067039A428 |
SHA-256 | 2E57B74257C6A5F36BEC8F49B91007882E236936F05F45CA561212EA0C1DC531 |
SSDEEP | 192:HwQHNMoY7BScDhUXMXVqVsr8sESkcSsK3n+4+Hge9:HwYMoY7BScDhUXMXVqKr8zSkcSsK3nTm |
TLSH | T1242212817682DA930E4201605D8D1192FE8EB87A96E97DFFCC6C90657004C5BC77F9DB |
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 |