# Differences between type-inheritance clause & protocol composition syntax? **URL:** \ **Category:** Using Swift\ **Tags:** compiler, inheritance, protocols, declarations, conformance\ **Created:** [May 6, 2021, 3:35pm UTC](https://forums.swift.org/t/differences-between-type-inheritance-clause-protocol-composition-syntax/47940 "2021-05-06T15:35:31Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![xAlien95](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/xalien95/32/12558_2.png) [@xAlien95](https://forums.swift.org/u/xAlien95)\ **Post date:** [May 6, 2021, 3:49pm UTC](https://forums.swift.org/t/differences-between-type-inheritance-clause-protocol-composition-syntax/47940/2 "2021-05-06T15:49:11Z")
> [@Is this a good idea? protocol IdentifiableHashable: Hashable, Identifiable { }](https://forums.swift.org/t/is-this-a-good-idea-protocol-identifiablehashable-hashable-identifiable/47496/11): > > While I don't really have any useful opinions on the main point you raised in your post, I can answer this question. slight_smile The answer is yes. A single inheritance clause with a protocol composition is equivalent to multiple inheritance clause entries where each one is a single protocol. There's also an interesting useless bit of trivia here. Could we hypothetically deprecate the , syntax for writing out multiple inheritance clause entries and always have a single one which might be a… --- _[View the full topic](https://forums.swift.org/t/differences-between-type-inheritance-clause-protocol-composition-syntax/47940)._