style(array): restore rustfmt on the files #8090 landed unformatted - #8107
Merged
Conversation
`cargo fmt --all -- --check` is red on main at 0d7fe21, in exactly the two files that commit touched: the `array::header` re-export list in `array/mod.rs` and the import block in `typed_array_receiver_tests.rs`. `lint` is a required context and #8087 had just restored it, so this put it straight back to red for every open PR. Formatting only -- no code, no re-export set change, `cargo fmt --all -- --check` clean afterwards. My fault at merge time: I ran the four static gates (file size, GC store-site inventory, raw-handle ratchet, addr-class inventory) on the landing tree and did not run `cargo fmt --check`, which is the one gate that catches this.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughChangesArray formatting cleanup
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 14, 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
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.
cargo fmt --all -- --checkis red onmainat0d7fe21b0, in exactly the two files #8090 touched — thearray::headerre-export list inarray/mod.rsand the import block intyped_array_receiver_tests.rs.lintis a required context and #8087 had only just restored it, so this put it back to red for every open PR, one day after #8092 documented that pattern.Formatting only. No code change, no change to the re-export set.
cargo fmt --all -- --checkis clean afterwards, and the other four gates (check_file_size.sh,gc_store_site_inventory.py,raw_handle_debt.py,addr_class_inventory.py) were already green and stay green.Mine to own: I merged #8090 after running those four static gates on the landing tree and did not run
cargo fmt --check, which is the one that catches this. Refs #8092.Summary by CodeRabbit