diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-07-26 00:57:21 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-26 00:57:21 +0200 |
| commit | ab2dd3aeb95c3ef5d7a34b2435f1f95472dabc08 (patch) | |
| tree | e53daac7f2d036b7c17adeeb5e0db2aba5407204 /tests/coverage/branch/lazy-boolean.coverage | |
| parent | 29314e4fca75b09404a2dfb3686179d0bdb78bce (diff) | |
| parent | c5dadd0408bc5654f001efe0f2224ff67e5e90a7 (diff) | |
| download | rust-ab2dd3aeb95c3ef5d7a34b2435f1f95472dabc08.tar.gz rust-ab2dd3aeb95c3ef5d7a34b2435f1f95472dabc08.zip | |
Rollup merge of #127950 - nnethercote:rustfmt-skip-on-use-decls, r=cuviper
Use `#[rustfmt::skip]` on some `use` groups to prevent reordering. `use` declarations will be reformatted in #125443. Very rarely, there is a desire to force a group of `use` declarations together in a way that auto-formatting will break up. E.g. when you want a single comment to apply to a group. #126776 dealt with all of these in the codebase, ensuring that no comments intended for multiple `use` declarations would end up in the wrong place. But some people were unhappy with it. This commit uses `#[rustfmt::skip]` to create these custom `use` groups in an idiomatic way for a few of the cases changed in #126776. This works because rustfmt treats any `use` item annotated with `#[rustfmt::skip]` as a barrier and won't reorder other `use` items around it. r? `@cuviper`
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.coverage')
0 files changed, 0 insertions, 0 deletions
