Recordscargosyn3.0.3
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | ubuntu glibc | |
|---|---|---|
| syn | 100%1 | 75%8 |
| syn::BinOp | 100%1 | 100%1 |
| syn::DeriveInput | 100%1 | 100%2 |
| syn::Expr | 100%1 | 100%2 |
| syn::ExprClosure | 100%1 | 100%2 |
| syn::ExprIf | 100%1 | 100%2 |
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.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
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 0✓ 2✕ · PROJECT_PROCESS 11✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 13 | 1 | 79% | 1 | 2026-09-17 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 4✓ · PROJECT_TEST 4✓ — Usage: USED 7✓ — Verified: CONTRACT 11✓
|
MEDIUM | 8 +7 | 11 | 100% | 2 · 2✓ | 2026-09-17 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 E0609 ×1 3.0.3 os=linux syn sha256:120b2f5dde9f…error[E0609]: no field `unsafety` on type `Signature`rust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-17 · Last seen: 2026-09-17
-
observed PROJECT_COMPILE exit 101 ×1 3.0.3 os=linux syn sha256:a85f4b192108…error: could not compile `sample-syn` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-17 · Last seen: 2026-09-17
Symbols
- syn 1 1 of 1 runs passed
- syn::BinOp 1 1 of 1 runs passed
- syn::DeriveInput 1 1 of 1 runs passed
- syn::Expr 1 1 of 1 runs passed
- syn::ExprBinary 1 1 of 1 runs passed
- syn::ExprClosure 1 1 of 2 runs passed
- syn::ExprIf 1 1 of 1 runs passed
- syn::ExprMatch 1
- syn::ExprMethodCall 1
- syn::File 1 1 of 1 runs passed
- syn::Item 1
- syn::ItemFn 1
- syn::Lit 1
- syn::Type 1
- syn::parse_str 1
Published samples
- syn 3.0.3 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-09-14