Regardless, yes, that’s the whole point. What’s been accepted is https://doc.rust-lang.org/nightly/core/arch/index.html , that is, intrinsics that map 1-1 to the vendor APIs. (I belive this is the same in C++ but not my area of specialty so I may be wrong)
https://doc.rust-lang.org/nightly/core/simd/index.html is the first level up the abstraction chain; this hasn’t gone through an RFC process yet, but will eventually happen.
On top of that, you have stuff like https://crates.io/crates/faster , which is very high level. Looks like they need to fix up the README... but you get the idea.
Also, autovectorization has existed this entire time. This stuff is for when that falls down.
Most compilers do a reasonable job with auto-vectorization, and if more is needed, there are instrisics.
No need to write straight Assembly.
Are the intrinsics standard? If so, what version of the standard were they in? How good is compiler support for them?
They are not portable between CPU architectures either way
For reference, C got real alignment support in C11 and C++ in C++17. Without this, even starting on SIMD is risky.
That said, you can go really far with a good C++ math library like Eigen which has singe vectorization in the operations themselves.