r? @epage

(rustbot has picked a reviewer for you, use r? to override)

ah I messed this up, sorry -- don't bother reviewing yet 😅

I'm actually a bit stuck here. The --all-targets doc block is shared between a number of different pages, and as far as I understand the caveat about doctests only really applies to cargo test and not, for example, cargo bench.

As one possibility, I could move the --all-targets doc to a separate "include" markdown file options-all-targets.md, then write a custom --all-targets doc block for cargo test. This would accomplish the goal, but at the cost of future edits to options-all-targets.md not being reflected in the cargo test page's entry for that flag.

What do you think @epage? Perhaps there's a better way?

Bleh, includes are difficult

Options

• Don't bother with this part of the change
• Duplicate the whole options-targets directly in cargo test
• Add a variable to customize the behavior of options-targets

Not thrilled with any of the options

Agreed, don't love any of them.

If you have a preference, I'm happy to do that. If not, I'll default to closing this and leaving a note about it in #6669 so it doesn't slip through the cracks and is readily found once the testing sub-team is up and running.

For me, the more important part is everything but what is in the shared documentation. Since you aren't feeling up for that, I lean towards closing.