[GSoC 2025] Interest in 'Re-implement Property Wrappers with Macros' Project

Hello, I'm Jacob. I am a senior BS/MS student at UNC-Chapel Hill. I have been making apps in Swift/SwiftUI for the past few years, and for most of that time, I have been helping other students learn Swift as a leader in a student organization and as a teaching assistant for UNC's Swift and SwiftUI course taught by @samrshi.

Since taking a course on programming languages last fall, I have been independently studying compilers, and getting more comfortable with C++ with the specific end goal of being able to contribute to the Swift compiler. GSoC seems like it would be a great opportunity to get to contribute and move closer to this goal!

I am particularly interested in this project because of the opportunity to expand upon Swift macro functionality, the potential to simplify the compiler through the removal of ad-hoc property wrapper code, and its impact on the greater Swift and SwiftUI community. The project also seems to align well with the languages ongoing push for innovation in the space of metaprogramming.

So far I have read through all of the resources linked in the projects description and created a local build of the compiler that I have started to tinker with. @xedin if you have any advice or resources that could guide me on next steps or help me prepare to write my proposal, it would be greatly appreciated!

Also, I figured it would be useful to pick up a ticket or two that is somewhat related to this project prior to submitting a proposal. I found the following tickets marked 'good first issue' that seemed at least adjacently related to the project. @xedin, would you recommend any of these in particular, or are there any others you think would be better?

(sorry in advance for the lengthy post :slightly_smiling_face:)

4 Likes

hey Jacob, is there a way for us to discuss this project in-depth as you and I may share the same vision for this project moving forward and would love to contribute in a long-term sope for this to work

Hey @ArihantMarwaha, would definitely be open to collaborate! After looking deeper into the rules for GSoC however, It seems like the projects are only allowed to be done individually. Maybe @ktoso or @xedin could chime in on what kind of collaboration is allowed?

Since my original post, I also noticed that someone may have put together a proposal / done some work on this issue last year. @xedin do you know if any progress was made on this that we could check out?

A GSoC project must be undertaken by a single applicant. Otherwise it'd be difficult to judge it a person is meeting goals or just tagging along etc. By having it be a single person it is clear if the project progress and goals are being met etc.

Collaborating is of course very welcome, but it would be outside of the GSoC "project" structure. GSoC after all is about open source so there is bound to be some collaboration with others in the OSS community, but I would recommend steering away from "sharing" a project.

If both of you are interested in the same project I'd request both to submit a proposal on the summer of code website, and we'll have to pick the best one which would be accepted into the program.

Hope this helps,

3 Likes