Codify how to group our imports #12063
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
|
Web viewer built successfully.
View image diff on kitdiff. Note: This comment is updated whenever you push a commit. |
timsaucer
approved these changes
Dec 2, 2025
emilk
added a commit
that referenced
this pull request
Dec 3, 2025
### Related * Follows #12063 ### What Runs `cargo +nightly fmt` to reformat all our `use` import statements according to our new guidelines. Yes, this is a lot of annoying churn, but enough people have complained about us not having a standard for this that I wanted to just fix this once and for all. …except it's not really once-and-for-all, because it is just really just _once_, for now. Still, it should make it easier to follow suit in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'll actually apply it once these PRs are merged: