Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/array_test.go |
FileSize | 5222 |
MD5 | EE15A7818AD9D1DF41B7D53AB9FC1005 |
SHA-1 | 0101D7EDFC9806FBC056D3622FC9DBA18717FD2C |
SHA-256 | E5E391D194DB453819E40860F2DD72F7654526E352E0C3DFA55015F12D156D3D |
SSDEEP | 96:RIwwQHNodo+hQ09UGhGUBSymtSp/loqgoZycPO4udY8sOFIEIh1bEwuZqD9pU5cd:HwQHNCphn9t2iWIUTqclu |
TLSH | T150B1CF749C037D2326416420068A3C55FACCA5AFD8D20DCAE41E8AAE6B7DDD1D5FD3B1 |
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 |