gitadmin/foxhunt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(ml-backtesting): allow(unsafe_code) on sim/mod.rs for cudarc launches

Browse Source 
cudarc kernel launches require `unsafe` blocks — the driver API has no
way to type-check kernel args against the cubin signature. The
workspace-wide `-W unsafe-code` lint produces noise on every launch
site (10+ blocks); suppressing at the module level keeps the lint
useful elsewhere in the crate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
jgrusewski
2026-05-19 23:50:31 +02:00
parent dc8c37e11e
commit 24a8b4c621
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
crates/ml-backtesting/src/sim/mod.rs
View File

@@ -6,6 +6,13 @@
//! //!
//! See docs/superpowers/specs/2026-05-18-real-lob-integration-design.md §2 + §5b. //! See docs/superpowers/specs/2026-05-18-real-lob-integration-design.md §2 + §5b.
// cudarc kernel launches are inherently `unsafe`: the driver API has no way
// to type-check kernel args against the .cubin's signature. Per
// pearl_no_host_branches_in_captured_graph + the surrounding GPU-contract
// pearls, all launches are pre-compiled and the args are matched by hand in
// review. The workspace-wide `-W unsafe-code` lint is therefore noise here.
#![allow(unsafe_code)]
mod batched_config; mod batched_config;
pub use batched_config::{BatchedSimConfig, ResolvedSimVariant, UniformSimParams}; pub use batched_config::{BatchedSimConfig, ResolvedSimVariant, UniformSimParams};