# \[Pitch\] Move Function + "Use After Move" Diagnostic

**URL:** <https://forums.swift.org/t/pitch-move-function-use-after-move-diagnostic/53983>\
**Category:** Pitches\
**Created:** [December 11, 2021, 1:22am UTC](https://forums.swift.org/t/pitch-move-function-use-after-move-diagnostic/53983 "2021-12-11T01:22:46Z")\
**Posts on this page:** 1\
**Showing post:** 97

<div class="post-metadata">

**Author:** ![Jumhyn](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jumhyn/32/3891_2.png) [@Jumhyn](https://forums.swift.org/u/Jumhyn)\
**Post date:** [December 14, 2021, 1:53pm UTC](https://forums.swift.org/t/pitch-move-function-use-after-move-diagnostic/53983/97 "2021-12-14T13:53:25Z")

</div>

> [@gwendal.roue](#):
>
> But you have seen that the motivation chapter of the pitch does not talk about `do { }` at all - and this is a hint that `move` is about a [more general language feature](https://github.com/apple/swift/blob/main/docs/OwnershipManifesto.md#move).

~~That~~ Thank you for linking the manifesto. It should be noted that the ownership manifesto is (years) [out-of-date](https://forums.swift.org/t/how-is-shared-keyword-supposed-to-work-in-swift-5-0/19803/5) in at least some regards, which is why I think it’s important for this proposal to be a self-contained justification for the feature it introduces.

If the elaboration required to explain how `move` fits into the ownership story is too large, or too irrelevant to the feature itself, then I think we need an updated version of the manifesto and/or a guiding document like the [concurrency roadmap](https://forums.swift.org/t/swift-concurrency-roadmap/41611) to help understand how ownership features will fit together.

If the rest of the ownership model isn’t at a point where it will be ready for review soon, I don’t really understand how we can properly evaluate the individual pieces.

---

_[View the full topic](https://forums.swift.org/t/pitch-move-function-use-after-move-diagnostic/53983)._