Affected area
- Rust core runtime
- Build, packaging, or CI
- Documentation or examples
Current behavior
The public fork_scope_stack example declares its helper as async fn example() -> nemo_relay::Result<()>, but the crate exports the alias as nemo_relay::error::Result.
As a result, the core doctest fails with E0425:
error[E0425]: cannot find type `Result` in crate `nemo_relay`
Expected behavior
The example should use the public path for the result alias, and the doctest should compile as part of the Rust test target.
Steps to reproduce
- Check out
main at 2ab7a070.
- Run
cargo test -p nemo-relay --doc fork_scope_stack.
- Observe that the example fails to compile before it can run.
Environment
- NeMo Relay commit:
2ab7a070
- OS and architecture: Ubuntu 26.04 LTS, x86_64
- Rust version: 1.96.1
- Install/build command:
cargo test -p nemo-relay --doc fork_scope_stack
Impact
The doctest stage of the Rust validation path reports a failure on a clean checkout. Contributors then need to distinguish this existing documentation failure from failures introduced by their changes. The current workaround is to skip the doctest or correct the result path locally.
Affected area
Current behavior
The public
fork_scope_stackexample declares its helper asasync fn example() -> nemo_relay::Result<()>, but the crate exports the alias asnemo_relay::error::Result.As a result, the core doctest fails with E0425:
Expected behavior
The example should use the public path for the result alias, and the doctest should compile as part of the Rust test target.
Steps to reproduce
mainat2ab7a070.cargo test -p nemo-relay --doc fork_scope_stack.Environment
2ab7a070cargo test -p nemo-relay --doc fork_scope_stackImpact
The doctest stage of the Rust validation path reports a failure on a clean checkout. Contributors then need to distinguish this existing documentation failure from failures introduced by their changes. The current workaround is to skip the doctest or correct the result path locally.