Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/zapcore/json_encoder.go |
FileSize | 13622 |
MD5 | 09123525B6E754F9082A06F32D3309F3 |
SHA-1 | 03B9D0DB860398CE61DAC923C6087E14A944CA39 |
SHA-256 | 033E7B589DEFEE887C8E6446589015DE829830F625CCC79CE3BD2644F5878DF4 |
SSDEEP | 384:HwYHFUCJjPqhf29Z1TuvMEh2RzD4FCWD6kaNgFEnsvZ7lz68MD8M02S3RzGl0R2x:pHFUCJWh+9Z1TuvMEh2RzD4FCs6kPCOe |
TLSH | T1DA525541A994D51BCD8936701990BAF961FCBEE40DE0359AFCDC37EA630568B86330F6 |
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 |