fearless_simd v1.0 is on its way: SIMD in Rust without writing unsafe. 🦀 By Shnatsel (Sergey Davidoff) and the Linebender team. Most Rust SIMD abstractions rely on substantial internal unsafe code. fearless_simd concentrates that boundary in a small, audited implementation layer, so user-facing SIMD code can be written without unsafe blocks. How: The kernel! macro uses Rust's target-feature machinery and type-level SIMD capability tokens to make many architecture-specific intrinsic calls safe at the call site. SIMD loads and stores ultimately operate on raw pointers. fearless_simd centralizes that handling in reusable safe-transmute wrappers, keeping the raw-pointer boundary in one auditable place. Two small, auditable building blocks. The rest of your SIMD code stays safe. What's also planned for v1.0: Hardware-width vector abstractions, allowing one algorithm to target suitable 128-, 256-, or 512-bit implementations through dispatch. → Fast and precise variants for operations such as swizzle and floating-point maximum, whose behavior can differ across platforms. → Safe access to platform intrinsics when portable abstractions aren't enough. fearless_simd_macros v0.1 with #[simd], providing function multiversioning without requiring #[inline(always)]. A planned three-year security-support commitment for v1.0 and later versions. Even if std::simd stabilizes, fearless_simd can continue to provide value through multiversioning, hardware-width vectors, dispatch, and ecosystem tooling. 🔗 linebender.org/blog/fearless… #RustLang #SIMD #Performance #OpenSource #SystemsProgrammin