On Tue, Nov 4, 2025 at 3:35 PM Guillaume Gomez <[email protected]> wrote: > > You can use `cfg(doc)` and `cfg(doctest)` to only include parts of the > docs when running doctests (if that's what this is about).
Thanks for the quick reply! I think this is more about having some code essentially "prefixed" to certain doctests without having to repeat it in every one. Or, more generally, to provide custom "environments" for certain doctests, including perhaps a custom prelude and things like that. So one way would be writing a `mod` (perhaps with a `path` attribute) or an `include` to manually do that. Or perhaps having an auxiliary crate or similar that contains those mods/files (that probably only gets built when the KUnit doctests are enabled). Orthogonally, the script that generates the doctests could perhaps help to automate some of that. For instance, we could have a way to specify an "environment" for a given Rust file or Rust `mod` or similar, and then every doctests would have the code prefixed to them. But I prefer to wait until we have real users of this and the new JSON generation. Using `cfg(doctest)` in some code in the `kernel` crate wouldn't work, unless I am missing something, because we wouldn't want to have a "parallel `kernel` crate" in the same build that only the doctests would use. Cheers, Miguel
