Move use rand::RngExt to test routines to avoid unused import#64
Merged
Nugine merged 1 commit intoNugine:mainfrom Mar 5, 2026
Merged
Move use rand::RngExt to test routines to avoid unused import#64Nugine merged 1 commit intoNugine:mainfrom
use rand::RngExt to test routines to avoid unused import#64Nugine merged 1 commit intoNugine:mainfrom
Conversation
Nugine
approved these changes
Mar 5, 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.
Thank you for reviewing #63 and for following up with two additional commits! Looking at the result, it occurred to me that it could be slightly nicer to move
use rand::RngExtinside the test functions that use it. Then it would be subject to the same conditional compilation as the test code, and it wouldn’t be necessary to add#[allow(unused_imports)].