Compiler unstable options for rustdoc? (any hack is fine)

โš“ Rust    ๐Ÿ“… 2025-12-01    ๐Ÿ‘ค surdeus    ๐Ÿ‘๏ธ 1      

surdeus

Any trick/override/inject/hack (in config files, Rust source, Linux env, filesystem/aliases...) so that
cargo +nightly test
would apply an equivalent of RUSTFLAGS="-Znext-solver=globally" to doctests, please?

It's for compile_fail doctests (the crate itself is stable-friendly, but that can be tested with stable separately). Primarily run in GitHub Actions, so I'm happy for any hack.
(I do see rustdoc: allow full set of compiler options to be specified ยท Issue #43031 ยท rust-lang/rust ยท GitHub and it's sad...)

Or: Any way to make the next solver the default one?

Or; Any way to make (parts) of doctests elevated to internal/compiler-like code (if there is any internal attribute that uses the next solver).

1 post - 1 participant

Read full topic

๐Ÿท๏ธ Rust_feed