As far as I can tell, regardless of whether the pointer itself is atomic, it doesn’t change the fact that the memory it points to, the underlying memory,is not. And therefore all the same arguments apply that were given to revoke UnsafePointer’s Sendable status as seen at UnsafePointer Sendable should be revoked
I definitely appreciate the reminder that having to spell out @unchecked brings here, it clearly puts the responsibility on me, the programmer, to get things right.
Conditionally Sendable seems the obvious choice here.