Recordscargosyn
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| syn | syn | syn::BinOp | syn::DeriveInput | syn::Expr | syn::ExprBinary | syn::ExprClosure | syn::ExprIf | |
|---|---|---|---|---|---|---|---|---|
| x64 | 100%8 | 100%1 | 100%1 | 100%1 | 100%1 | 100%1 | 100%1 | 100%1 |
Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
How to read the grid
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.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.0.3
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:120b2f5dde9fce592cd7cfeecb9fd13b68fc9e8d3e35ed9c074c0c7cbc3829a6
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| unicode-ident | 1.0.24 | CANDIDATE Correlated change; unproven combination | contract passed | 43 project-days |
| unicode-ident | 1.0.25 | CANDIDATE Correlated change; unproven combination | builds observed | 11 project-days |
| unicode-ident | 1.0.26 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| proc-macro2 | 1.0.107 | PASS All observations passed | contract passed | 61 project-days |
| quote | 1.0.47 | PASS All observations passed | contract passed | 60 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 3.0.6 | 3.0.5 | 3.0.3 | 2.0.119 |
|---|---|---|---|---|
| unicode-ident | 1.0.25 | 1.0.25 | 1.0.26 | 1.0.25 |
| proc-macro2 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 |
| quote | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 |
Moved: 1 · unchanged at every release: 2
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.