# \[GSoC 2026\] Re-implement Property Wrappers with Macros — contribution history + proposed plan (Flamki)

**URL:** <https://forums.swift.org/t/gsoc-2026-re-implement-property-wrappers-with-macros-contribution-history-proposed-plan-flamki/85498>\
**Category:** GSoC\
**Created:** [March 23, 2026, 8:17am UTC](https://forums.swift.org/t/gsoc-2026-re-implement-property-wrappers-with-macros-contribution-history-proposed-plan-flamki/85498 "2026-03-23T08:17:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flamki](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/flamki/32/44613_2.png) [@Flamki](https://forums.swift.org/u/Flamki)\
**Post date:** [March 23, 2026, 8:17am UTC](https://forums.swift.org/t/gsoc-2026-re-implement-property-wrappers-with-macros-contribution-history-proposed-plan-flamki/85498/1 "2026-03-23T08:17:57Z")

</div>

Hi Swift community,

I’m Ayush Singh (GitHub: @Flamki), a final-year B.Tech student applying for GSoC 2026. I’m interested in the “Re-implement property wrappers with macros” project.

Recent related compiler work:

- Merged: [PropertyWrappers] Better diagnostic for invalid enclosing-self subscript types (#87403) — [[PropertyWrappers] Better diagnostic for invalid enclosing-self subscript types by Flamki · Pull Request #87403 · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/pull/87403)
- Follow-up by @xedin: [Diagnostics] PropertyWrappers: Allow enclosing-self subscript to accept read-only key path (#87680) — [[Diagnostics] PropertyWrappers: Allow enclosing-self subscript to acc… by xedin · Pull Request #87680 · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/pull/87680)
- Open: [PropertyWrappers] Allow out-of-line init for read-only wrappers (#87802) — [[PropertyWrappers] Allow out-of-line init for read-only wrappers by Flamki · Pull Request #87802 · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/pull/87802)
- Open: [Sema] Fix crash with peer macro-generated wrapped properties (#87601) — [[Sema] Fix crash with peer macro-generated wrapped properties by Flamki · Pull Request #87601 · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/pull/87601)

These gave me hands-on experience with property-wrapper behavior across AST/Sema paths, proposal-conformance fixes, diagnostics, and regression testing.

Proposed GSoC approach:

- Behavior parity first: proposal-conformance + regression coverage before broader refactoring.
- Initial scope: stored properties in nominal types (macro + init-accessor path).
- Then expand to macro/wrapper integration gaps and known crashers.
- Keep each milestone incremental, reviewable, and test-backed.

@xedin I’d value your guidance before I finalize my proposal:

1. Is “stored properties first, then broader wrapper scenarios” the right order for 2026?
2. Which milestones should be must-have vs stretch for a successful GSoC term?

Happy to share a week-by-week draft after your feedback.

Thanks,  
Ayush (@Flamki)

---

<div class="post-metadata">

**Author:** ![xedin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/xedin/32/309_2.png) [@xedin](https://forums.swift.org/u/xedin)\
**Post date:** [March 27, 2026, 9:29pm UTC](https://forums.swift.org/t/gsoc-2026-re-implement-property-wrappers-with-macros-contribution-history-proposed-plan-flamki/85498/2 "2026-03-27T21:29:59Z")

</div>

Hello and thank you for the interest in the project!

> Is “stored properties first, then broader wrapper scenarios” the right order for 2026?

Yes, I think we should concentrate on the bits that are covered by existing macro functionality first and proceed incrementally.

> Which milestones should be must-have vs stretch for a successful GSoC term?

I think any new macro capabilities are most likely a stretch goal since we won't be able to get them through evolution.

---

<div class="post-metadata">

**Author:** ![Flamki](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/flamki/32/44613_2.png) [@Flamki](https://forums.swift.org/u/Flamki)\
**Post date:** [March 29, 2026, 7:06am UTC](https://forums.swift.org/t/gsoc-2026-re-implement-property-wrappers-with-macros-contribution-history-proposed-plan-flamki/85498/3 "2026-03-29T07:06:42Z")

</div>

Thank you @xedin — that makes sense.

I’ll scope the proposal around existing macro functionality first, with behavior parity + regression coverage as the core deliverable, and keep any new macro capability work as stretch only.
