# Automatic Requirement Satisfaction in plain Swift

**URL:** <https://forums.swift.org/t/automatic-requirement-satisfaction-in-plain-swift/37158>\
**Category:** Pitches\
**Created:** [June 2, 2020, 7:06pm UTC](https://forums.swift.org/t/automatic-requirement-satisfaction-in-plain-swift/37158 "2020-06-02T19:06:11Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![saeta](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/saeta/32/6264_2.png) [@saeta](https://forums.swift.org/u/saeta)\
**Post date:** [June 2, 2020, 11:03pm UTC](https://forums.swift.org/t/automatic-requirement-satisfaction-in-plain-swift/37158/7 "2020-06-02T23:03:15Z")

</div>

> [@anandabits](#):
>
> In addition to preserving invariants, exposing a structural representation reduces encapsulation of implementation details. Exposing the guts of a type is not necessary for the current compiler generated synthesis.

Thanks for the response @anandabits! Could you describe your concerns a bit further? I'd like to understand a little bit better. Thanks!

Note: I'm guessing a little bit, but if I'm understanding your concerns correctly, I think we attempted to allude to this in the following section:

> [@shabalin](#):
>
> The Structural protocol—like Swift’s Mirrors—exposes a type’s internal implementation. In order to enable the use of Structural generic programming within libraries that provide a stable API & ABI (e.g. are compiled for library evolution), please see the related pitch

The related pitch is here: [Scoped Conformances](https://forums.swift.org/t/pitch-non-public-conformances-implementing-public-api/37159). That said, it's quite possible we have forgotten about something, so please do let us know what we've missed!

---

_[View the full topic](https://forums.swift.org/t/automatic-requirement-satisfaction-in-plain-swift/37158)._
