Pre-RFC: RArrow for Pointer Ergonomics

[toc]

Some previous discussion:

Need for -> operator for Unsafe Code Guidelines

I lost a long detailed draft of this, so I’ll keep it short this time. In my experience, the two most common miri-caught violations of the Unsafe Code Guidelines we have are: We materialize or hold onto a too-large reference when working with raw pointers We mess up pointer alignment in low-level code, often in niche cases like with ZSTs This post is about the former. I am bothered by the former because it tends to be the consequence of a common problem: it’s a pain in the neck to offset a ra…