Commit 8d95b4f
committed
Update malachite to 0.11
`malachite-bigint` 0.11.0 released while the workspace pinned 0.10.0. `pymath`
requires `malachite-bigint = "0"`, so a fresh resolve picks 0.11 for it and
leaves the workspace on 0.10, putting two incompatible copies of `BigInt` in
one graph. `crates/stdlib/src/math.rs` then fails to compile, which is what the
example projects do -- they carry no lockfile and resolve fresh on every run.
`malachite-q` and `malachite-base` move with it; bumping `malachite-bigint`
alone splits `malachite-nz` the same way. No source change is needed.
Assisted-by: Claude1 parent b0b4d2f commit 8d95b4f
2 files changed
Lines changed: 12 additions & 12 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -246,9 +246,9 @@ log = "0.4.30" | |||
| 246 | 246 | lz4_flex = "0.13" | |
| 247 | 247 | nix = { version = "0.31", features = ["fs", "user", "process", "term", "time", "signal", "ioctl", "socket", "sched", "zerocopy", "dir", "hostname", "net", "poll"] } | |
| 248 | 248 | mac_address = "1.1.3" | |
| 249 | - malachite-bigint = "0.10.0" | ||
| 250 | - malachite-q = "0.10.0" | ||
| 251 | - malachite-base = "0.10.0" | ||
| 249 | + malachite-bigint = "0.11.0" | ||
| 250 | + malachite-q = "0.11.0" | ||
| 251 | + malachite-base = "0.11.0" | ||
| 252 | 252 | md-5 = "0.11" | |
| 253 | 253 | memchr = { version = "2.8.1", default-features = false, features = ["alloc"] } | |
| 254 | 254 | memmap2 = "0.9.10" | |
0 commit comments