Tracking Issue for Rust 2024: Rustdoc tests in one binary

[traviscross]

This is a tracking issue for compiling all rustdoc tests in one binary.

• Greatly speed up doctests by compiling compatible doctests in one file #123974
• Rustdoc should run all doctests in one binary #75341

About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

• Implement in nightly Rust 2024.
  • Greatly speed up doctests by compiling compatible doctests in one file #123974
  • Greatly speed up doctests by compiling compatible doctests in one file #126245
• N/A Implement migration lints.
  • We just want to document the breakage in the migration guide.
• N/A: Add documentation to the dev guide.
  • See the instructions.
• N/A: Add documentation to the reference.
  • See the instructions.
• Add documentation to the edition guide.
  • 2024: Add rustdoc combined doctests edition-guide#320
  • Rename doctest standalone tag edition-guide#325
  • Add some tips for what to be careful of with rustdoc-doctests edition-guide#323
• Ensure ready for Rust 2024 stabilization.

Unresolved Questions

TODO.

Related

• Greatly speed up doctests by compiling compatible doctests in one file #123974
• rustdoc: Refactor doctest collection and running code #125798
• Greatly speed up doctests by compiling compatible doctests in one file #126245
• doctests testing-devex-team#5

cc @epage @GuillaumeGomez

[ehuss]

Posted draft of the documentation at rust-lang/edition-guide#320

[traviscross]

@rustbot labels +S-tracking-ready-for-edition

We reviewed this in our edition call today. This item is ready for Rust 2024.

Thanks to @GuillaumeGomez for pushing this important work forward, and thanks to all the reviewers for providing helpful feedback.

[GuillaumeGomez]

Thanks for writing the edition explanations! :D