Reopening of #13739: rustdoc: Inline reexported items if possible. #14012
Conversation
some examples to look at: `std::io`, `std::prelude`, `libc`. there are some known exceptions to inlining (e.g. statics), so they are preserved to the reexport section as much as possible. it would be desirable to remove such exceptions in the future.
|
So I was looking at that screenshot and was wondering how to make it shorter since it is very verbose esp. when it appears repeatedly. Something else: do we want to add some margin before the text so that we can set the marker aside? (So that lines with reexported marker line up with those that don't have it) |
|
@adrientetar A concise icon would be helpful indeed. I'm less sure if the |
|
Closing due to inactivity, but feel free to reopen with a rebase! |
Adding section for Visual Studio IDE Rust development support This PR adds a section for Rust support in Visual Studio IDE.
Expand docs section on Visual Studio to mention all three available extensions A recent PR (rust-lang#14012) by `@parthopdas` added mention of rust-analyzer.vs, his extension for Visual Studio 2022. I am submitting this PR to request that our extension (SourceGear Rust) be mentioned in that section as well, and also, for completeness, the VS_RustAnalyzer extension, by `@cchharris.` Our extension is closed source, so I have clearly disclosed that. For consistency, I included brief mention of the licenses for the other two options as well. Also for the sake of consistency, I added marketplace and GitHub links for all 3. The previously added paragraph by `@parthopdas` about his extension has been left intact.
Mostly fixes #13045. See #13739 for the screenshots and detailed discussion; the main change remains same. I completely forgot to rebase in spite of #13777 (which also alters the very same files) being merged...