You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Nothing compiles the cuda_* imports in markdown #1761
Imports in markdown are compiled by nothing. A ```rust fence in the book or a README never reaches a build, so a use cuda_core::... line keeps compiling only as long as someone notices it has gone stale. `status-guard.yml` says as much above `host-api-paths`: "Nothing compiles book, README, or `cargo oxide new` snippets, which is how some forty stale lines outlived the crate switch." The guards that exist all read source text:
check-host-api-paths.sh pattern-matches the removed SIMT namespace.
check-book-api-names.sh checks device-API call names against cuda_device.
Neither catches an import of a host item that has been renamed or moved.
I ran a probe on main (8d82548). It compiles every use cuda_device|cuda_host|cuda_core|cuda_async|cuda_bindings::... from rust fences in tracked markdown, each path in its own module of a throwaway crate. All 125 distinct paths, from 34 pages, resolve today. So a guard would land green and only fail on new rot.
I'll open the PR: the probe as scripts/check-doc-use-paths.py, wired into just check-guards and into examples-compile, the job that already has the CUDA toolkit cuda-bindings needs.
Activity