You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This crates uses allocator-api2 without exposing a feature to enable #![feature(allocator_api)].
Due to issues outlined here zakarumych/allocator-api2#19,
this makes it is impossible to have this crate anywhere in the dependency tree along with hashbrown when enabling the hashbrown/nightly feature.
The text was updated successfully, but these errors were encountered:
Tried to run `cargo update`, but that broke things, see
rust-lang/hashbrown#564.
Updated:
- itertools to 0.14
- kiddo to 5
- petgraph to 0.7
- notify to 8
- wasmtime and wasmtime-wasi to 29
Note: this causes even bigger problems if one were to try to run
`cargo update` since even if one were to add certain transitive
dependencies to common/Cargo.toml and enable the necessary feature
flags, a transitive dependency here also depends on allocator-api2 but
without exposing the proper feature flag. A fix is underway, see
bytecodealliance/regalloc2#209
- axum to 0.8
- discord-sdk to 0.4
- minifb to 0.28
This crates uses
allocator-api2
without exposing a feature to enable#![feature(allocator_api)]
.Due to issues outlined here zakarumych/allocator-api2#19,
this makes it is impossible to have this crate anywhere in the dependency tree along with
hashbrown
when enabling thehashbrown/nightly
feature.The text was updated successfully, but these errors were encountered: