I'm complaining that the object I've built will have literal memcpy(3) called on it.

At a certain point, the compiler can’t save you and you have to actually know the limitations of the data you’re working with.

I do know how, as I listed how to in my original comment: using Pin. It's just been very unergonomic in a couple cases because I don't actually care in some of those cases of the struct is copied, I just want know when &self's bit pattern changes and there's no way in rust to know that.