Skip to content

Conversation

jakubDoka
Copy link
Contributor

this resolves problems with feature unification
and resolves #209

this resolves problems with feature unification

Signed-off-by: Jakub Doka <[email protected]>
@jakubDoka
Copy link
Contributor Author

@cfallin
Copy link
Member

cfallin commented Jan 27, 2025

@jakubDoka feel free to update the GitHub CI configuration too: the all-features check can probably instead become a list of cargo check invocations with specific feature sets, e.g. no default features; std; std, checker; std, trace-log; std, serde; serde. Or something like that? Then separately a cargo +nightly check --features allocator-api?

@hanna-kruppe
Copy link

The need to do this has been resolved by updates to hashbrown (rust-lang/hashbrown#606 solves the specific problem with hashbrown/nightly) and allocator-api2 (zakarumych/allocator-api2#30 solves it for everyone else).

@Amanieu
Copy link
Contributor

Amanieu commented Apr 30, 2025

This should now be fixed with the latest release of hashbrown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't use with hashbrown/nightly feature
4 participants