# Update on implementation-only imports

**URL:** <https://forums.swift.org/t/update-on-implementation-only-imports/26996>\
**Category:** Compiler\
**Created:** [July 16, 2019, 12:07am UTC](https://forums.swift.org/t/update-on-implementation-only-imports/26996 "2019-07-16T00:07:42Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![mmfl](https://avatars.discourse-cdn.com/v4/letter/m/7bcc69/32.png) [@mmfl](https://forums.swift.org/u/mmfl)\
**Post date:** [October 11, 2019, 9:55pm UTC](https://forums.swift.org/t/update-on-implementation-only-imports/26996/9 "2019-10-11T21:55:56Z")

</div>

I just wrote a post on my experiences splitting a package into modules ([Swift packages and module dependencies](https://forums.swift.org/t/swift-packages-and-module-dependencies/29741) ) where one of the issues I raised was automatic "re-export" of conformances and extensions added to imported public types. My suggestion was

> [@Swift packages and module dependencies](https://forums.swift.org/t/swift-packages-and-module-dependencies/29741/1):
>
> Could we e.g. use a syntax something like `import X as internal` to stop conformances and extensions added to public type X being "re-exported"?

but hopefully this feature will deal with this issue!

---

_[View the full topic](https://forums.swift.org/t/update-on-implementation-only-imports/26996)._