Don't use *move* in `Pin` documentaton about rust HOT 7 OPEN

I do feel like this is weird:

For the purposes of this module’s documentation, however, when we write move in italics, we mean specifically that the value has moved in the mechanical sense of being located at a new place in memory.

Of these options, the only one that makes sense is perhaps relocate.

from rust.

I still agree that we don't necessarily need to overload verbs with rust-specific meanings just for convenience in these docs, and italicization is a pretty small thing to distinguish MOVE.for-the-purposes-of-borrowck and MOVE.relocate-bytes-in-memory.

from rust.

I think that it's also helpful to say somewhere that a semantic move usually means a bitwise move too

from rust.

Huh? I have read that passage in the Pin docs several times and my takeaway has always been that it is in fact using the meaning usually specified in Rust.

from rust.

I wonder if on top of being a hindrance to understanding by most, it would be show-stopper for people relying on a screen reader, or whose vision is otherwise impaired.

I don't have a strong opinion regarding the chosen term, but as a native speaker of a latin tongue (French) both "relocated" and "displaced" seem clear.

from rust.

I wonder if on top of being a hindrance to understanding by most, it would be show-stopper for people relying on a screen reader, or whose vision is otherwise impaired.

No. I mean, depends on the screen-reader, but the words are HTML-tagged. They should be responsive to <em> and <strong> and are off-spec if they aren't.

from rust.

Yeah, I think I saw it as a refinement of the usual sense but I can see how it can be confusing, having given it more thought.

I don't think simply swapping words is quite what we want, either, though.

from rust.