I&#x27;m surprised to see no mention in the article or on HN about how this might affect writing crypto code in Rust. Maybe it&#x27;s a little tangential, but I&#x27;m dying for constant time operations.<p>Avoiding branches, etc. in Rust doesn&#x27;t mean LLVM won&#x27;t add some as an optimization, which is frustrating to say the least. It would be awesome to be able to define a block - similar to &quot;unsafe&quot; - that tells the compiler to disable optimizations that could introduce non-constant time operations. When I started reading the article, I though maybe this new development would open the door to something like that, but it doesn&#x27;t appear to be the case.<p>There&#x27;s some work to do constant time ops in rust, but it&#x27;s very experimental and untrustworthy. :&#x2F;