The core team believes that property behaviors are a worthwhile feature for Swift, but it’s clear from the discussion that we as a community have not yet converged on a design we are willing to commit to. It is therefore too early to accept a proposal for this feature. We encourage the author to continue refining the design and providing new proposal drafts for discussion, and will schedule another public review when it looks like we are closer to converging on a single design.
The core team believes that property behaviors are a worthwhile feature
for Swift, but it’s clear from the discussion that we as a community have
not yet converged on a design we are willing to commit to. It is therefore
too early to accept a proposal for this feature. We encourage the author to
continue refining the design and providing new proposal drafts for
discussion, and will schedule another public review when it looks like we
are closer to converging on a single design.
When will be a good time to discuss this proposal again?
I think Apple's usual policy is that Swift 4 will ship with iOS 11 (so end of September, I think). Then they have a break, and sometime after that planning for Swift 5 starts. That’s probably the best time to bring it up so it can be weighed against other priorities.
So it’ll be a little while yet.
- Karl
···
On 11. Jul 2017, at 17:41, Wallacy via swift-evolution <swift-evolution@swift.org> wrote:
Em qua, 24 de fev de 2016 às 04:14, Douglas Gregor via swift-evolution <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> escreveu:
The review of SE-0030 “Property Behaviors” ran from February 10...23, 2016. The proposal in its current form is rejected:
The core team believes that property behaviors are a worthwhile feature for Swift, but it’s clear from the discussion that we as a community have not yet converged on a design we are willing to commit to. It is therefore too early to accept a proposal for this feature. We encourage the author to continue refining the design and providing new proposal drafts for discussion, and will schedule another public review when it looks like we are closer to converging on a single design.