# Default Package Swift Settings

**URL:** <https://forums.swift.org/t/default-package-swift-settings/71872>\
**Category:** Pitches\
**Created:** [May 15, 2024, 5:24pm UTC](https://forums.swift.org/t/default-package-swift-settings/71872 "2024-05-15T17:24:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![NeoNacho](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/neonacho/32/1368_2.png) [@NeoNacho](https://forums.swift.org/u/NeoNacho)\
**Post date:** [May 15, 2024, 6:04pm UTC](https://forums.swift.org/t/default-package-swift-settings/71872/3 "2024-05-15T18:04:27Z")

</div>

I think the pitch makes sense at a high-level.

> [@mattie](#):
>
> Per-target settings would be merged with higher precedence.

I think this will need a lot more concrete design, potentially with different merging strategies based on the type of settings. For example, Xcode has a pretty sophisticated model here, with multi- and single-value settings, `$(inherited)` etc -- a lot of the cases that solves will likely come up in a multi-layer build settings model for SwiftPM as well.

There's also the question of how to address potential ambiguity with `swiftLanguageVersion` (see [SE-0435](https://forums.swift.org/t/accepted-se-0435-swift-language-version-per-target/71846)) since that would also be part of `SwiftSetting` now, but there's an existing package level property for this already.

---

_[View the full topic](https://forums.swift.org/t/default-package-swift-settings/71872)._