# Pitch: Weak method storage modifiers (aka weak references)

**URL:** <https://forums.swift.org/t/pitch-weak-method-storage-modifiers-aka-weak-references/12161>\
**Category:** Pitches\
**Created:** [April 26, 2018, 2:58am UTC](https://forums.swift.org/t/pitch-weak-method-storage-modifiers-aka-weak-references/12161 "2018-04-26T02:58:12Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![eneko](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/eneko/32/12117_2.png) [@eneko](https://forums.swift.org/u/eneko)\
**Post date:** [July 3, 2018, 11:03pm UTC](https://forums.swift.org/t/pitch-weak-method-storage-modifiers-aka-weak-references/12161/17 "2018-07-03T23:03:43Z")

</div>

I realized I never got back to you on this one. Sorry.

I was wrong on the way I expressed myself, so my assertion was incorrect. The point I was trying to make is that while retain cycles can happen with in a single class (like the example from my original post), they can al so happen with other classes: A retains B and B retains A.

Back to my original pitch, we currently prevent this with closures by using `[weak self]` or `[unowned self]`, but we don't have a way to achieve the same with direct method references, which is a bummer.

Thanks

---

_[View the full topic](https://forums.swift.org/t/pitch-weak-method-storage-modifiers-aka-weak-references/12161)._
