diff options
| author | bors <bors@rust-lang.org> | 2022-04-22 02:30:27 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-04-22 02:30:27 +0000 |
| commit | 8b2393086f4c41007b5fb02ef0579ffa7046bff2 (patch) | |
| tree | 263a9f1a9deda26bb0056b231c849caa1f6cf7f2 /compiler/rustc_codegen_llvm/src | |
| parent | 0b3404b01b251401e6b45cb1c4df8f883dfab2d7 (diff) | |
| parent | 7803a411517f0f1e64d8f37ce377c684d1f2d1fd (diff) | |
| download | rust-8b2393086f4c41007b5fb02ef0579ffa7046bff2.tar.gz rust-8b2393086f4c41007b5fb02ef0579ffa7046bff2.zip | |
Auto merge of #96282 - petrochenkov:unindent, r=GuillaumeGomez
rustdoc: Unindent doc fragments on `Attributes` construction `Attributes` can be constructed at arbitrary points, even after the `unindent_comments` pass. `Attributes` that are constructed too late end up unindented. All doc fragments need to be eventually indented before use, so there are no reasons to not do this immediately during their construction. Fixes https://rust-lang.zulipchat.com/#narrow/stream/266220-rustdoc/topic/.60unindent_comments.60.20cannot.20work.20as.20a.20separate.20pass. I'm not sure how to make a minimized reproduction, but unindenting the fragments during their construction should fix the issue.. by construction, and I also verified that all doc strings now hit the `resolver_caches.markdown_links` cache in https://github.com/rust-lang/rust/pull/94857.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions