# Protocol extensions inheriting protocols

**URL:** <https://forums.swift.org/t/protocol-extensions-inheriting-protocols/25491>\
**Category:** Pitches\
**Created:** [June 9, 2019, 1:58pm UTC](https://forums.swift.org/t/protocol-extensions-inheriting-protocols/25491 "2019-06-09T13:58:27Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![DevAndArtist](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/devandartist/32/287_2.png) [@DevAndArtist](https://forums.swift.org/u/DevAndArtist)\
**Post date:** [June 9, 2019, 6:57pm UTC](https://forums.swift.org/t/protocol-extensions-inheriting-protocols/25491/4 "2019-06-09T18:57:22Z")

</div>

@johnno1962 does this basically make your patch equivalent to the following idea?

> [@Protocol metatype extensions (to better support SwiftUI)](https://forums.swift.org/t/protocol-metatype-extensions-to-better-support-swiftui/25469/1):
>
> `extension some P` extends conforming types onyl (not the existential or the metatype)

If we had to use `any`, `some` and potentially `meta` explicitly then it feels like you're proposing to allow to write `extension some P : Q { ... }`. Am I correct?

---

_[View the full topic](https://forums.swift.org/t/protocol-extensions-inheriting-protocols/25491)._