[swift-evolution] [Proposal] Property behaviors

[David Waite]

Interesting. I suppose that answers my question - the desire to have container references and initialization data presented during storage/retrieval (so that they do not need to be duplicated inside the wrapper type) resulted in types being required to look more like plugins to the type system rather than simple wrappers.

-DW

> On Jan 13, 2016, at 10:53 PM, Brent Royal-Gordon <brent at architechies.com> wrote:
> 
>> I was wondering if you had considered/had comments an alternative approach where you declare an ordinary new value type which meets certain rules and ‘wraps’ the existing type, then define new syntax/features in Swift for having the wrapper (or possibly even multiple levels of wrappers) be more transparent for use.
> 
> You might want to take a look at the first version of the proposal. It defined behaviors using existing constructs with certain conventions, and most posters argued that it was a bit of a mess and needed syntax to clarify what was happening.
> 
> -- 
> Brent Royal-Gordon
> Architechies
>