Repository navigation
style: standardize imports across the workspace - #364
Merged
Merged
Conversation
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.
Summary
Standardize Rust imports across the library, tests, benchmarks, examples, and doctests. Start ordinary intra-crate imports at
crate::, retain localpub use self::...re-exports, and reuseuse super::*in unit tests. Preserve original symbol names and meaningful qualifiers, such asiter::onceandtokio::time::sleep, to make the operation and its source or runtime clear. Document these conventions inAGENTS.md. Public APIs and behavior are unchanged.Validated with
cargo x lint,cargo x check(26 feature configurations),cargo x test(595 tests, including doctests), andcargo x bench -- --test(both benchmark targets).