You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, if /// C is not included, the code is left unformatted (this is what I would expect whether /// C is there or not).
As far as I can tell, this reproducing example is minimal: for example, after removing d: usize we do not reproduce the reported behavior.
I found this issue while adding rustdocs to an existing project.
I would expect that adding a line of documentation should not cause the formatting of the code to change.
The text was updated successfully, but these errors were encountered:
ytmimi
changed the title
Adding a docstring inside an enum causes a change in the enum formatting
Adding a doc comment inside an enum causes a change in the enum formatting
Aug 14, 2024
Test case as reported in rust-lang#6280.
This test case used to fail, but the code in the previous commit fixes
it.
We followed instructions on Contributing.md [1] to create a test case.
`tests/target/rust-doc-in-enum/vertical-no-doc.rs` is being left unformatted
(expected behavior), while `tests/target/rust-doc-in-enum/vertical-with-doc.rs`
is formatted to `C { a: usize }` (unexpected behavior).
The only different between the two samples is the `/// C` rustdoc added
in `with-doc.rs`.
This reproducing example is minimal: for example, after removing `d: usize`
we do not reproduce the reported behavior.
We found this issue while adding rustdocs to an existing project.
We would expect that adding a line of documentation should not cause the
formatting of the code to change.
[1] https://github.com/rust-lang/rustfmt/blob/40f507526993651ad3b92eda89d5b1cebd0ed374/Contributing.md#L33
I include a reproduction of the issue in #6279.
The following minimal example is being formatted.
The resulting format is:
However, if
/// C
is not included, the code is left unformatted (this is what I would expect whether/// C
is there or not).As far as I can tell, this reproducing example is minimal: for example, after removing
d: usize
we do not reproduce the reported behavior.I found this issue while adding rustdocs to an existing project.
I would expect that adding a line of documentation should not cause the formatting of the code to change.
The text was updated successfully, but these errors were encountered: