@mcc Thankfully Rust has the Strict Provenance APIs on its raw pointer types that let you do that masking (and unmasking) while not having to worry about provenance at all because it's properly handled by construction (just avoid everything that includes "exposed_provenance" or "without_provenance" in its name).
@pthariensflame I like it when Rust makes implicit properties of compilers explicit