CodeSampleX

Recordscargoclap_builder4.6.7

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

4○ 42026-10-22
alpine muslubuntu glibc
clap_builder::Arg 100%1 100%1
clap_builder::ArgAction 100%1 100%1
clap_builder::Command 100%1 100%1
clap_builder::value_parser 100%1 100%1

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment Confidence Observations Verified Pass rate Peers Last seen
unknown · Rust · cargo · linux glibc
Observations: PROJECT_PROCESS 8✓ · PROJECT_TEST 9✓
LOW 17 0 100% 1 2026-10-22
rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
LOW 2 +2 1 100% 1 · 1✓ 2026-10-22

Symbols