# Swift Concurrency: Feedback Wanted!

**URL:** <https://forums.swift.org/t/swift-concurrency-feedback-wanted/49336>\
**Category:** Discussion\
**Created:** [June 7, 2021, 7:31pm UTC](https://forums.swift.org/t/swift-concurrency-feedback-wanted/49336 "2021-06-07T19:31:38Z")\
**Posts on this page:** 1\
**Showing post:** 138

<div class="post-metadata">

**Author:** ![Douglas\_Gregor](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/douglas_gregor/32/1362_2.png) [@Douglas\_Gregor](https://forums.swift.org/u/Douglas_Gregor)\
**Post date:** [July 7, 2021, 12:04am UTC](https://forums.swift.org/t/swift-concurrency-feedback-wanted/49336/138 "2021-07-07T00:04:07Z")

</div>

> [@technogen](#):
>
> Quick question: If `Actor types do not support inheritance` , then why is `final actor` legal?

Right now, `final` still has an ABI impact, where it means "something that will never ever be subclassed or overridden". The [Core Team guidance](https://forums.swift.org/t/accepted-with-modification-se-0306-actors/47662#inheritance) on actor inheritance is that it is not part of the proposal, but they/we did not shut the door on it completely. Allowing `final` lets us keep the door open in the ABI and language to change our minds if actor inheritance turns out to be very important, and we can ban it later on if we decide that Swift will never have actor inheritance.

Doug

---

_[View the full topic](https://forums.swift.org/t/swift-concurrency-feedback-wanted/49336)._
