Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/field.go |
FileSize | 16559 |
MD5 | D1CFCD3B1E9B2C9AFD2E42FD79710CB7 |
SHA-1 | 04B706BE213BC820E5B41D150685A6FCDE13502C |
SHA-256 | ED7725F6A67FC877C9B9ADCE52814E3CD691224AF21E96A3DFF547A5DFD643F8 |
SSDEEP | 384:HwYUy/gfIuJoNTpwi4nK4o3V77ikgmsAon7+zamJ:p/gfIuJoNTpwiwK4o3V/i7mbon7kH |
TLSH | T1A272034076C2DAD24E4104A05D4C1283FEDDFC7699BCBEFACCA59062B40885BD27F9DA |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 86176 |
MD5 | 37CA6DAE3ADA414F5354F3F9D985D5D6 |
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.14.1-1ubuntu1 |
SHA-1 | ACD9E9FF286E106F7D4F2EDBB4ABBD6739E1EB7E |
SHA-256 | 15D0790218FDDD217CDCBD65C3BA22AAAFDA0E3BE51524909AAF105648FED7A6 |
Key | Value |
---|---|
MD5 | 3F874FAAB3DF62EA9055B57CBA79CB49 |
PackageArch | noarch |
PackageDescription | 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. This package contains the source code needed for building packages that reference the following Go import paths: – go.uber.org/zap |
PackageMaintainer | Fedora Project |
PackageName | golang-uber-zap-devel |
PackageRelease | 1.fc32~bootstrap |
PackageVersion | 1.13.0 |
SHA-1 | 1F97DE2C352A35F31A46DE604C45B6203E98F110 |
SHA-256 | 58ACC78A47AEDE8DA8783024D0F857EF360AA72C047BDF5DB6CC1B4575682B28 |