Repository navigation
ml-kem: fix unstable name collision warnings - #393
Merged
Merged
Conversation
tarcieri
approved these changes
Oct 10, 2026
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
2 participants
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.
This addresses the warnings in #308 by replacing
u8::truncateandu16::truncatewithTruncate::truncate. It also removes the temporary#[allow(unstable_name_collisions)]attributes added in #320.The conversions themselves haven't changed. I also tested with
integer_widen_truncateenabled on nightly. The original code fails to compile, while the updated code builds and passes all ML-KEM tests.I haven't addressed the possible
Truncatemethod rename mentioned in #308. Happy to look into that separately if needed.