I&#x27;m not sure that&#x27;s the best example. In that case, the knowledge that the &#x27;array&#x27; global never has its address taken allows you to perform the optimization. You can also rewrite it by copying &#x27;array&#x27; to a separate local that doesn&#x27;t have its address taken, and ordinary SSA construction solves the problem.<p>I feel like a new systems language needs to come and make aliasing explicit in a way, so that it doesn&#x27;t surprise programmers but still allows them to get the optimizations that they want. Tracking uniqueness like Rust is a good first step, but it doesn&#x27;t work for unsafe code or anything with more subtle aliasing relationships.