rustdoc: mechanism for taking/handling arbitrary rustc arguments? #46189
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
T-rustdoc
Relevant to the rustdoc team, which will review and decide on the PR/issue.
Right now, rustdoc takes a handful of compilation-focused arguments so it can affect the compilation process it uses to extract docs or run tests. A discussion in
#cargo
today made me wonder if it was possible (or even feasible) to take arbitraryrustc
arguments and have some way to parse those into the required structures or features needed forrustdoc
's purposes as a compiler driver. Something like having--
and then batching everything that goes after that?@rust-lang/compiler @rust-lang/dev-tools @rust-lang/t-dev-tools-docs
The text was updated successfully, but these errors were encountered: