# An odd error: "Escaping closure captures mutating 'self'"

**URL:** <https://forums.swift.org/t/an-odd-error-escaping-closure-captures-mutating-self/50118>\
**Category:** Using Swift\
**Tags:** closure, escapingclosure\
**Created:** [June 30, 2021, 5:42am UTC](https://forums.swift.org/t/an-odd-error-escaping-closure-captures-mutating-self/50118 "2021-06-30T05:42:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rayx](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/rayx/32/12204_2.png) [@rayx](https://forums.swift.org/u/rayx)\
**Post date:** [June 30, 2021, 9:54am UTC](https://forums.swift.org/t/an-odd-error-escaping-closure-captures-mutating-self/50118/4 "2021-06-30T09:54:59Z")

</div>

@tem I find the answer. I didn't read through SE-0035 carefully. It says the following (highlighting is added by me):

> I propose we make it so that **implicitly** capturing an `inout` parameter into an escapable closure is an error.

> Capturing an `inout` parameter, including `self` in a `mutating` method, becomes an error in an escapable closure literal, **unless the capture is made explicit (and thereby immutable)**

That explains it!

---

_[View the full topic](https://forums.swift.org/t/an-odd-error-escaping-closure-captures-mutating-self/50118)._