Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/internal/readme/readme.go |
FileSize | 6694 |
MD5 | 487DECC341308E8E4B223B54E20F567C |
SHA-1 | 17D3379D4E4B421C847AEBA9FAE068AFE05487AD |
SHA-256 | 984FC58782902F8403B093A931E910DD3D300D97A20974BC008B37A0A155A979 |
SSDEEP | 192:HwQHNANplAUlZ/ZBl1B5FFvJn/wryV7mJ8rJrnHJK32JnUt00crGEXOFX1tYbuLV:HwYK5xXfJ05pKjYWG |
TLSH | T1F1D17549AA75430B0ACA00A06C55CDB5FDD4D6A33B3958B6FCDEB0EBA34803E517C7A4 |
hashlookup:parent-total | 7 |
hashlookup:trust | 85 |
The searched file hash is included in 7 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 649BD8D3AD412F6DD0B1D3D684E2A32C |
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 | 2.fc34~bootstrap |
PackageVersion | 1.16.0 |
SHA-1 | 80D16CFC670AB202DFEF8DD8CC523D969EE7AFF4 |
SHA-256 | 84E5783B51661AADD1999AE2EEDEAD23D2562BB15A9FE3FDBEBBAA2E71453458 |
Key | Value |
---|---|
FileSize | 92776 |
MD5 | 463934FF12514BB1A8F45D731B29A10E |
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 | Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> |
PackageName | golang-go.uber-zap-dev |
PackageSection | devel |
PackageVersion | 1.15.0-2 |
SHA-1 | 2A93B1CC72771914E1B673000A067C90FBDDEE01 |
SHA-256 | 0CDAC253B584EA850C1A61AF7A4EA1AEA957F688A8051496A09F20E4ACEC6D52 |
Key | Value |
---|---|
MD5 | 47A68BF9C6A09B72919B63AEC8ECA69E |
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.fc33~bootstrap |
PackageVersion | 1.15.0 |
SHA-1 | 2EC6DE9A609788C3396CEE87EA1255D211593692 |
SHA-256 | 93F895FBE3ED42336EED23C4F84995F8BFBBE97CF2743345B48297A55FEE16C4 |
Key | Value |
---|---|
MD5 | 2843D52B720A5785EC1E4D57E0FDC5EC |
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 | pterjan <pterjan> |
PackageName | golang-uber-zap-devel |
PackageRelease | 1.mga8 |
PackageVersion | 1.16.0 |
SHA-1 | 67550E2A2CDC3260BE44D531112828FFB36D3595 |
SHA-256 | FA4B01EA521E2AA3E2F82425F9E81A2DF25168EC4B96D487C31EE2A1287046C7 |
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 |
Key | Value |
---|---|
FileSize | 87816 |
MD5 | A0C8D3D844D38B74B8E35D7DE5158AF3 |
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.15.0-2 |
SHA-1 | 5B5C6CD7ED038AA74AEE6001F451A0F8E90605FF |
SHA-256 | 2E5492FACBCE91134B209D1457138E578D1D5E5EE551340D6D295D0214FE31E3 |
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 |