Recordsgolangmodernc.org/memory
Change the conditions
Current conditions
modernc.org/memory @v1.11.0glibc · x64 · go (version not recorded) · go
package-level total, not an API
0 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 2 / 2
- Contract verifications
- 0 / 2
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-27
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · go (version not recorded) · go
0 of 2 passed
Verified — this network ran a contract at this coordinate.
-
windows 11 · x64 · go (version not recorded) · go
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.11.0
windows · go@1.26
269 FAIL · stage: PROJECT_TEST
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 | v1.12.0 | v1.11.0 | v1.5.0 |
|---|---|---|---|
| golang.org/x/sys | v0.47.0 | v0.46.0 | — |
| modernc.org/mathutil | v1.7.1 | v1.7.1 | v1.5.0 |
Moved: 2 · unchanged at every release: 0
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.