dual-runtime-check

To verify Rust code compiles across tokio and monoio runtime feature sets, run the six verification steps that execute cargo build, clippy, and tests for both runtime configurations. This catches feature-gate or API-difference regressions before committing.

Checking dual runtime compatibility in a CI pipeline involves running repeatable verification steps for both runtime-tokio and runtime-monoio feature gates. The process reports pass or fail with detailed error context for runtime-adjacent changes.

Rust projects fail clippy checks when switching between runtime-tokio and runtime-monoio due to feature-gate or API-difference regressions. Running cross-runtime clippy verification before commits identifies these compatibility issues early.

Yes, you can run dual runtime compile checks as a pre-commit hook. The verification process provides repeatable steps integrating into pre-commit pipelines to ensure both tokio and monoio configurations compile and pass tests.

You need to run cross-runtime verification for your Moon project codebase before touching runtime-adjacent changes. This ensures compatibility across runtime-tokio and runtime-monoio feature sets by validating compilation, clippy, and tests.

When verifying dual runtime configurations with cargo, limitations involve potential feature-gate or API-difference regressions between runtime-tokio and runtime-monoio. The checks report pass or fail with detailed error context but require both feature sets present.