# About reassigning self in classes

**URL:** <https://forums.swift.org/t/about-reassigning-self-in-classes/33813>\
**Category:** Using Swift\
**Created:** [February 14, 2020, 8:10am UTC](https://forums.swift.org/t/about-reassigning-self-in-classes/33813 "2020-02-14T08:10:41Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Jens](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jens/32/12903_2.png) [@Jens](https://forums.swift.org/u/Jens)\
**Post date:** [February 14, 2020, 1:20pm UTC](https://forums.swift.org/t/about-reassigning-self-in-classes/33813/5 "2020-02-14T13:20:00Z")

</div>

Yes, this:

> [@Mutating Function on Class Type (Possible bug?)](https://forums.swift.org/t/mutating-function-on-class-type-possible-bug/15066/8):
>
> So it's left out of the language to avoid introducing a point of confusion.

answers the first question:

> [@Jens](#):
>
> Why is it important to prevent reassigning self in classes?

But not the second:

> [@Jens](#):
>
> Why is it not prevented to (even accidentally) do so via a protocol's default implementation?

If the following is your answer to that second question:

> [@Lantua](#):
>
> Reassigning self in protocol doesn’t seem to have as many interpretation.

Then I can't see what you mean by that.

---

_[View the full topic](https://forums.swift.org/t/about-reassigning-self-in-classes/33813)._