(That's about the underlying pointer-aliasing model visible to unsafe code; the sort of questions that come up with C's "restrict".) I don't think coming up wi

(That's about the underlying pointer-aliasing model visible to unsafe code; the sort of questions that come up with C's "restrict".) I don't think coming up with answers to those questions need have blocked writing that part of the reference manual. One alternative would be to document what aliasing guarantees rustc currently does and doesn't pass down to LLVM, along with what (if any) promises Rust is making about which things that therefore currently have defined behaviour at the LLVM level will also do so in the final language model. The point is that the current reference manual should document the compiler-writers' current understanding of what is allowed.