# Pitch: System in the toolchain

**URL:** <https://forums.swift.org/t/pitch-system-in-the-toolchain/84247>\
**Category:** Pitches\
**Created:** [January 20, 2026, 5:42pm UTC](https://forums.swift.org/t/pitch-system-in-the-toolchain/84247 "2026-01-20T17:42:29Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![tshortli](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/tshortli/32/15850_2.png) [@tshortli](https://forums.swift.org/u/tshortli)\
**Post date:** [February 12, 2026, 1:32am UTC](https://forums.swift.org/t/pitch-system-in-the-toolchain/84247/35 "2026-02-12T01:32:25Z")

</div>

> [@Michael\_Ilseman](#):
>
> My understanding of Swift's compilation model (which is a couple years out of date) is that there is no technical reason why this would be a breaking change, so long as it occurs between modules that are versioned together. There is some internal tooling for this purpose ([`@_originallyDefinedIn`](https://github.com/swiftlang/swift/blob/main/docs/ReferenceGuides/UnderscoredAttributes.md#_originallydefinedinmodule-modulename-availabilityspec)), but I'm not familiar with their current limitations.

Declarations can move between modules in the toolchain in both a source stable and ABI stable manner using a combination of re-exports and use of the `@_originallyDefinedIn` attribute. Source stability is preserved by introducing an `@_exported import` of the new module to the old module, ensuring that clients of the old module import the new module implicitly. `@_originallyDefinedIn` preserves the mangling of the symbols and also leaves metadata on the symbols which ld/dyld use to ensure that the symbol is expected in the right dylib at launch depending on which OS version the binary is running on. And finally the old dylib needs to be configured to re-export the new dylib so that clients do not need to be explicitly configured to link the new dylib.

Practically speaking the only direction declarations can move, though, is down. The new home of a moved declaration should either be an existing, lower level module or a new module which is layered below the previous owner. The new module approach is usually the wisest, since the `@_exported import` that is necessary does have source compatibility concerns if it means that an existing module might be implicitly imported in more clients where conflicts might arise.

---

_[View the full topic](https://forums.swift.org/t/pitch-system-in-the-toolchain/84247)._
