# The ambiguity of \`where\` clause to the reader

**URL:** <https://forums.swift.org/t/the-ambiguity-of-where-clause-to-the-reader/13709>\
**Category:** Discussion\
**Created:** [June 15, 2018, 12:05pm UTC](https://forums.swift.org/t/the-ambiguity-of-where-clause-to-the-reader/13709 "2018-06-15T12:05:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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 15, 2018, 12:14pm UTC](https://forums.swift.org/t/the-ambiguity-of-where-clause-to-the-reader/13709/3 "2018-06-15T12:14:58Z")

</div>

Well as it's right now there is no way to allow conditional conformances directly from the type declaration, and I'm not trying to say that we ever should, but just noting this fact. If we ever would want that feature then the reused `where` clause for constraints would become ambiguous.

Here is some bikeshedding code:

```swift
struct Generic<T> : Codable where T : Codable constraints T : Hashable { ... } 

```

The only requirement for `T` is to conform to `Hashable` while there is also a included conditional conformance.

Again that's just a few thoughts I had, not a pitch, just wanted to ask what others might think of it. ;)

---

_[View the full topic](https://forums.swift.org/t/the-ambiguity-of-where-clause-to-the-reader/13709)._