# Allowing \`guard let self = self else { … }\` for weakly captured self in a closure

**URL:** <https://forums.swift.org/t/allowing-guard-let-self-self-else-for-weakly-captured-self-in-a-closure/931>\
**Category:** Discussion\
**Created:** [January 6, 2016, 12:02am UTC](https://forums.swift.org/t/allowing-guard-let-self-self-else-for-weakly-captured-self-in-a-closure/931 "2016-01-06T00:02:21Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Chris\_Lattner](https://avatars.discourse-cdn.com/v4/letter/c/bc8723/32.png) [@Chris\_Lattner](https://forums.swift.org/u/Chris_Lattner)\
**Post date:** [January 23, 2016, 1:51am UTC](https://forums.swift.org/t/allowing-guard-let-self-self-else-for-weakly-captured-self-in-a-closure/931/12 "2016-01-23T01:51:29Z")

</div>

To confirm what others have said down thread, this is a compiler bug: this code is valid, but shouldn’t change what references to “self.method()” or “method()" bind to (i.e., explicit or implicit references to self).

Backquotes are for forming a name that happens to overlap with a keyword. In the case of `self`, this could be because you want to refer to the NSObject.`self` method for some reason. Backquotes are not a way to name self, init, subscript or any of the other declarations that look like magic identifiers.

-Chris

> **···**
>
> > On Jan 5, 2016, at 8:21 PM, Christopher Rogers via swift-evolution \<swift-evolution@swift.org\> wrote:
> > 
> > You can shadow self with a guard like you wrote it if use the keyword escaping backquotes like so:
> > 
> > guard let `self` = self else { return }

---

_[View the full topic](https://forums.swift.org/t/allowing-guard-let-self-self-else-for-weakly-captured-self-in-a-closure/931)._
