# \[Accepted with modification\] SE-0258: Property Wrappers

**URL:** <https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828>\
**Category:** Announcements\
**Created:** [July 10, 2019, 8:16pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828 "2019-07-10T20:16:42Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_McCall](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/john_mccall/32/1351_2.png) [@John\_McCall](https://forums.swift.org/u/John_McCall)\
**Post date:** [July 10, 2019, 8:16pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/1 "2019-07-10T20:16:42Z")

</div>

The [third review](https://forums.swift.org/t/se-0258-property-wrappers-third-review/26399) of [SE-0258](https://github.com/apple/swift-evolution/blob/master/proposals/0258-property-wrappers.md) has concluded. There was a lot more great discussion in this review, and while there were some questions and reservations, overall the community expressed strong support for accepting the proposal. The Core Team agrees and has decided to **accept** SE-0258 with only one minor change: we would like to accept the community's suggestion that the `initialValue:` argument label on wrapper initializers be renamed to `wrappedValue:` to match the property name. The Core Team feels that this is a minor enough change to make without a further round of review.

This has been a long and fruitful evolution review, encompassing three separate formal review periods and quite a few rounds of pitching and redevelopment. As the review manager, I appreciate how the community has handled itself throughout this process. It is a goal of evolution to not merely pass judgment on proposals but to ensure that they are as good as they can be, and I think SE-0258 has been a model for that in many ways. We now have a far better language design than we started with, and for that the credit goes both to the adaptability and patience of the authors and to the persistence and energy of the community. By thinking hard about the feel of the feature, by pushing on its expressive potential, and by actually trying it out and relaying back its strengths and weaknesses, the community has shaped and improved it immeasurably.

I say this in every review, and I mean it honestly: thank you for helping to make Swift a better language.

John McCall  
Review Manager

---

<div class="post-metadata">

**Author:** ![John\_McCall](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/john_mccall/32/1351_2.png) [@John\_McCall](https://forums.swift.org/u/John_McCall)\
**Post date:** [July 10, 2019, 9:26pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/2 "2019-07-10T21:26:39Z")

</div>

Split this topic on July 10, 2019, 9:26pm UTC

6 posts were merged into an existing topic: [Question about nested property wrappers and mutability](https://forums.swift.org/t/question-about-nested-property-wrappers-and-mutability/26830/4)

---

<div class="post-metadata">

**Author:** ![thuroe](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/thuroe/32/11564_2.png) [@thuroe](https://forums.swift.org/u/thuroe)\
**Post date:** [May 6, 2020, 3:46pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/3 "2020-05-06T15:46:12Z")

</div>

I do not know if this is the right place to ask the question, please redirect me as needed if this is the wrong place.  
My question is how the update to the documentation for evolutions is made available, and how the update of the existing documentation is happening?  
Like many others I have had a hard time following the changes in the Combine API over the last year.  
API documentation mostly provide a simplified documentation on how to use the API, but I was thinking a little differently.  
In the case of property wrappers there has been so many changes the past year that a changelog with old and new modified names would be very helpful.  
Maybe it already exists?  
Regards  
Lars  
Swift newbie

---

<div class="post-metadata">

**Author:** ![DevAndArtist](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/devandartist/32/287_2.png) [@DevAndArtist](https://forums.swift.org/u/DevAndArtist)\
**Post date:** [May 6, 2020, 7:21pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/4 "2020-05-06T19:21:17Z")

</div>

There were almost no changes to PWs after they got accepted. The only changes that happened were after WWDC19. The current design is fully described in the Property Wrapper proposal on the `swift-evolution` repository.

If you want to stay up to date, I recommend to follow the evolution repo or the linked webpage.

---

<div class="post-metadata">

**Author:** ![thuroe](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/thuroe/32/11564_2.png) [@thuroe](https://forums.swift.org/u/thuroe)\
**Post date:** [May 6, 2020, 8:18pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/5 "2020-05-06T20:18:24Z")

</div>

Thank you for the answer and the link.  
I find the documentation quite overwhelming, and indeed part discussion around the creation of the proposal and documentation.  
Please, I am not being critical, but it is an architectural document, and I was more looking for a comprehensive user (developper) documentation.  
People like me do not have the capacity, nor the wish to be a language architect.  
My objective is to have pleasure developing with Swift, and maybe in some years this kind of lecture will be for me, but for the time being I need something simpler.

Lars  
Swift newbie

---

<div class="post-metadata">

**Author:** ![Douglas\_Gregor](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/douglas_gregor/32/1362_2.png) [@Douglas\_Gregor](https://forums.swift.org/u/Douglas_Gregor)\
**Post date:** [May 6, 2020, 8:23pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/6 "2020-05-06T20:23:15Z")

</div>

The Swift Programming Language has a section on property wrappers: [Properties — The Swift Programming Language (Swift 5.7)](https://docs.swift.org/swift-book/LanguageGuide/Properties.html)

---

<div class="post-metadata">

**Author:** ![Lantua](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/lantua/32/8868_2.png) [@Lantua](https://forums.swift.org/u/Lantua)\
**Post date:** [May 6, 2020, 8:24pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/7 "2020-05-06T20:24:20Z")

</div>

If you have the [Swift Programming Language](https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewBook?id=881256329) book (e-book version of @Douglas_Gregor‘s link), there’s a revision history at the end of it.

Also [`Combine`](https://developer.apple.com/documentation/combine?changes=latest_minor) doc has options to show difference between versions (usually in the top-right corner)

---

<div class="post-metadata">

**Author:** ![thuroe](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/thuroe/32/11564_2.png) [@thuroe](https://forums.swift.org/u/thuroe)\
**Post date:** [May 6, 2020, 8:26pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/8 "2020-05-06T20:26:56Z")

</div>

Thank you to everybody.  
Those links are more in my ballpark I think

---

<div class="post-metadata">

**Author:** ![DevAndArtist](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/devandartist/32/287_2.png) [@DevAndArtist](https://forums.swift.org/u/DevAndArtist)\
**Post date:** [May 6, 2020, 8:28pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/9 "2020-05-06T20:28:23Z")

</div>

I didn‘t know that, haven‘t re-read the book for years now. Good to know.

---

<div class="post-metadata">

**Author:** ![Lantua](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/lantua/32/8868_2.png) [@Lantua](https://forums.swift.org/u/Lantua)\
**Post date:** [May 6, 2020, 8:29pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/10 "2020-05-06T20:29:04Z")

</div>

To be fair, it’s not clear what, uhh, level of _technicality_ you’re looking for originally.

---

<div class="post-metadata">

**Author:** ![wowbagger](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wowbagger/32/13847_2.png) [@wowbagger](https://forums.swift.org/u/wowbagger)\
**Post date:** [May 7, 2020, 12:23am UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/11 "2020-05-07T00:23:00Z")

</div>

> [@Lantua](#):
>
> If you have the [Swift Programming Language](https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewBook?id=881256329) book (e-book version of @Douglas_Gregor‘s link), there’s a revision history at the end of it.

It's online too on [swift.org](http://swift.org): [The Swift Programming Language: Redirect](https://docs.swift.org/swift-book/RevisionHistory/RevisionHistory.html)

---

<div class="post-metadata">

**Author:** ![thuroe](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/thuroe/32/11564_2.png) [@thuroe](https://forums.swift.org/u/thuroe)\
**Post date:** [May 7, 2020, 6:07am UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/12 "2020-05-07T06:07:59Z")

</div>

Sorry for being unclear. I think that it was unclear to myself as well 🙂I appreciate all help given.  
Lars  
Swift newbie

---

<div class="post-metadata">

**Author:** ![ajedwards](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ajedwards/32/36084_2.png) [@ajedwards](https://forums.swift.org/u/ajedwards)\
**Post date:** [February 18, 2021, 5:33pm UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/13 "2021-02-18T17:33:18Z")

</div>

After re-reading the accepted proposal, I still wasn't clear on the answer to this question: Is there a path forward to allow for the ability to access `self` of the enclosing type (not the wrapper type) within the initial value of a stored property (such as a closure) when used in conjunction with a property wrapper?

The accepted proposal mentions how `lazy` could not be completely implemented as a property wrapper because of this point, but also disallows the use of `lazy` with property wrappers, which seems to leave functionality to be desired. Is there a future direction that allows for this? I can imagine some really interesting use cases if this were possible.

**As a note** : While I may have overlooked it, I couldn't find a specific reason stating why `lazy` is disallowed with property wrappers (other that the fact that there may be a future attempt to replace most of `lazy`'s utility with a `@Lazy` property wrapper).

---

<div class="post-metadata">

**Author:** ![carlhung](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/carlhung/32/4446_2.png) [@carlhung](https://forums.swift.org/u/carlhung)\
**Post date:** [February 24, 2021, 4:25am UTC](https://forums.swift.org/t/accepted-with-modification-se-0258-property-wrappers/26828/14 "2021-02-24T04:25:44Z")

</div>

> [@ajedwards](#):
>
> e completely implemented as a property wrapper because of this point, but also disallows the

I also tried creating `lazy` property wrapper, but accessing `self` doesn't allow.  
I want to create a constant using `lazy` property wrapper.
