# \[Pitch\] Adoption tooling for upcoming features

**URL:** <https://forums.swift.org/t/pitch-adoption-tooling-for-upcoming-features/77936>\
**Category:** Pitches\
**Created:** [February 18, 2025, 11:50am UTC](https://forums.swift.org/t/pitch-adoption-tooling-for-upcoming-features/77936 "2025-02-18T11:50:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![FranzBusch](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/franzbusch/32/19447_2.png) [@FranzBusch](https://forums.swift.org/u/FranzBusch)\
**Post date:** [February 18, 2025, 4:03pm UTC](https://forums.swift.org/t/pitch-adoption-tooling-for-upcoming-features/77936/2 "2025-02-18T16:03:32Z")

</div>

This is great! We recently pitched an overhauled version of [Extensible enums for non resilient modules](https://forums.swift.org/t/pitch-extensible-enums-for-non-resilient-modules/77649) that is using a language feature to change the behavior of enums inside a module. This would be a perfect candidate to offer an _adoption_ mode where each existing public enum in the module would generate a warning with a fix-it to add `@frozen` to it in preparation to turning the language feature to avoid any API breaks.

---

_[View the full topic](https://forums.swift.org/t/pitch-adoption-tooling-for-upcoming-features/77936)._