# Revisiting requiring explicit \`self.\` when passing a method as an escaping closure

**URL:** <https://forums.swift.org/t/revisiting-requiring-explicit-self-when-passing-a-method-as-an-escaping-closure/12149>\
**Category:** Pitches\
**Created:** [April 25, 2018, 7:24pm UTC](https://forums.swift.org/t/revisiting-requiring-explicit-self-when-passing-a-method-as-an-escaping-closure/12149 "2018-04-25T19:24:21Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![dabrahams](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/dabrahams/32/9815_2.png) [@dabrahams](https://forums.swift.org/u/dabrahams)\
**Post date:** [May 3, 2018, 5:20pm UTC](https://forums.swift.org/t/revisiting-requiring-explicit-self-when-passing-a-method-as-an-escaping-closure/12149/17 "2018-05-03T17:20:03Z")

</div>

IMO if we're going to make a change in this area that increases the requirement for classes, we should be thinking about decreasing it for other types. The compiler also [seems](https://forums.swift.org/t/explicit-capture-semantics-applied-too-broadly/11737) to force explicit `self` in many cases where there's no good reason for it.

---

_[View the full topic](https://forums.swift.org/t/revisiting-requiring-explicit-self-when-passing-a-method-as-an-escaping-closure/12149)._