Support preserve_order in no_std builds - #1333
Open
razmser wants to merge 1 commit into
Open
Conversation
razmser
force-pushed
the
no-std-preserve-order
branch
from
July 22, 2026 17:02
958abbf to
5faf8b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
preserve_ordercurrently impliesstd(since #885), so it cannot be enabled inno_std+allocbuilds.Make it imply
allocinstead, usingRandomStatewithstdandrustc_hash::FxBuildHasherwithout it.Compatibility:
default-features = false, features = ["preserve_order"]now produces an alloc-only build rather than implicitly enabling std.Security: the deterministic
FxHasherused byno_stdbuilds is not HashDoS-resistant. Existingstdbuilds are unaffected.