# Constrain protocol usage outside the module

**URL:** <https://forums.swift.org/t/constrain-protocol-usage-outside-the-module/8832>\
**Category:** Pitches\
**Created:** [January 25, 2018, 9:03am UTC](https://forums.swift.org/t/constrain-protocol-usage-outside-the-module/8832 "2018-01-25T09:03:18Z")\
**Posts on this page:** 1\
**Showing post:** 64

<div class="post-metadata">

**Author:** ![anandabits](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/anandabits/32/355_2.png) [@anandabits](https://forums.swift.org/u/anandabits)\
**Post date:** [January 31, 2018, 3:58am UTC](https://forums.swift.org/t/constrain-protocol-usage-outside-the-module/8832/64 "2018-01-31T03:58:09Z")

</div>

@xwu that is a straw man. Nobody is talking about shipping closed protocols with no conforming types.

Closed protocols are different in that it is less common for a library to want to ship one. But they are still a valid design technique and there is value in having a consistent design policy of reserving flexibility for library authors by default. This change may not be possible anymore but it is certainly a valid position to believe it would be better than what we currently have.

---

_[View the full topic](https://forums.swift.org/t/constrain-protocol-usage-outside-the-module/8832)._
