Key | Value |
---|---|
FileName | ./usr/share/gocode/src/go.uber.org/zap/zapio/writer.go |
FileSize | 4520 |
MD5 | A4199D012AF402730B80359CBCE7383A |
SHA-1 | 1788C6E63F0FB579A4229646155E2E58292D109B |
SHA-256 | 5E4F6BCA12F7D78C88325B8376971CB832625A997D31CB06327C042AEEDDF182 |
SSDEEP | 96:bIwwQHNomo5wdfwuplXLOybo9KrcpbkxcC/gA8wCLqBzktwmu:9wQHNlo5Lupl7Oy+dyxgwCLqBcw1 |
TLSH | T172918611ABDE037317403129314CDBD5B694E26FEA3D6B65E06CA078A31903CE1765F2 |
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 |
---|---|
MD5 | 2458C40B8127863CC0B72879B7D4B5E8 |
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 | umeabot <umeabot> |
PackageName | golang-uber-zap-devel |
PackageRelease | 2.mga9 |
PackageVersion | 1.18.1 |
SHA-1 | 11147AE851C6901D835A2C94C47CF524B2F87FA8 |
SHA-256 | F67AE07372C5905A0CEF9018A02E22E0E5779C981F1937C566E37A00B0E9A5BA |