The definition of !Move was always the (rather baroque) "cannot be moved once its address has been taken;" this allowed you to construct them, allocate them, et

The definition of !Move was always the (rather baroque) "cannot be moved once its address has been taken;" this allowed you to construct them, allocate them, etc until you start manipulating them. Pin just took that contract and instead expressed it by having the value that is "the address of the !Move type" encode it. The questions with adding Move were strictly around backward compatibility & useability, not with determining the semantics.