CodeSampleX

Recordscargoblock-buffer0.12.1

Which symbol ran where

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

5 62026-11-14
alpine muslubuntu glibc
block_buffer::EagerBuffer 100%2 100%5
block_buffer::Error 100%2 83%12
block_buffer::LazyBuffer 100%2 71%7
block_buffer::ReadBuffer 100%2 100%5
block_buffer::array::Array 78%9
block_buffer::array::typenum::U4 100%2 73%15

Showing the environments with the most evidence.

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_COMPILE 2✓ 4✕ · PROJECT_PROCESS 6✓ · PROJECT_TEST 6✓ — Verified: UNKNOWN 0✓ 1✕
ELEVATED FAILURE 18 1 74% 1 2026-11-08
rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 4✓ · PROJECT_TEST 4✓ — Usage: USED 5✓ — Verified: CONTRACT 6✓
LOW 8 +5 6 100% 1 · 1✓ 2026-11-14

Recent failure clusters

Symbols

Published samples