zlob

Why it's ranked here

The case rests on unusually broad scope paired with deliberate performance engineering. Pattern analysis avoids irrelevant directories, common extension sets compile to SIMD bitmasks, and directory walking uses platform-specific system interfaces. The repository also documents compatibility tests drawn from several established implementations. The strongest speed figures remain project-reported benchmarks, not independent validation.

What's good

One engine serves filesystem discovery, in-memory filtering, and direct file walking across three languages. Compiled patterns support allocation-free repeated matching. The walker offers parallel collection or callbacks, selective metadata retrieval, depth and thread controls, ignore-rule filtering, symlink cycle protection, and optional input-order-preserving batch results.

Tradeoffs

Modern behavior is flag-driven, so defaults require attention. Ignore filtering, extended patterns, hidden-file matching, and symlink traversal are not all enabled together by the recommended glob settings. Unsorted output is favored for speed. Rust consumers also need Zig installed during ordinary native builds, while documentation builds skip that native compilation.

How to use it well

Use it in C, Zig, or Rust tools that repeatedly search large trees, filter existing path batches, or need traversal with selective metadata. Compile recurring patterns and process paths in batches. Choose collection for maximum throughput and callbacks when retaining every entry wastes memory. It does not provide a general content-search engine.

Observed

Primary implementation language

Zig, with C and Rust public bindings

Interfaces

C library, native Zig module, Rust crate, and command-line executable

Build outputs

Shared library, static library, C header, and CLI executable

Rust packaging

Published crate builds the bundled native library through Zig and generates bindings with bindgen

Platform support

Linux, macOS, iOS, Windows, FreeBSD, NetBSD, and Android targets are represented

Test structure

Build targets run Zig tests, C API tests, Rust tests, and libc comparison tests