> The function name "move" here is beyond terrible. It makes sense only to compiler writers, and even then it is ambiguous. These are exactly the sorts of issu

> The function name "move" here is beyond terrible. It makes sense only to compiler writers, and even then it is ambiguous. These are exactly the sorts of issues that an evolution proposal is supposed to shake out. It gives users a chance to weigh in on new features, including naming, before they land in the language or standard library. The name is very much not finalized yet, and comments pointing toward a better binding for the functionality would be welcome.