> This pitch is breaking, and should be considered under the phase 1 timeframe.
> gist here:https://gist.github.com/erica/f5c58c689a6f479606c6158077c1962b

I don’t agree with this proposal, 



PS: The first alternative might be useful though:  “… Swift could still warn or 
error on  set(oldValue), willSet(oldValue), and didSet(newValue), since these 
can be considered to be always wrong."

swift-evolution mailing list

Reply via email to