Swift semantics can be unduly confusing and complicated. "copy on write" value semantics mean you can have two variable references to the same memory for a lon

Swift semantics can be unduly confusing and complicated. "copy on write" value semantics mean you can have two variable references to the same memory for a long time before one mutation causes the space to be copied and mutated, leaving the other unaffected. The function name "move" here is beyond terrible. It makes sense only to compiler writers, and even then it is ambiguous. The function's goal/effect is to end the lifetime of a variable binding, to essentially force the COW. (So much for scoping.) More generally, Swift grows in fits and starts mostly driven by Apple internal needs. So if Apple needs `move(x)`, you might, too. Poor Swift team: fully exposed in open-source, but driven and locked to Apple's needs. All the best to them.