[swift-evolution] Pitch: Omit deprecation warnings for same-file references

Brent Royal-Gordon brent at architechies.com
Sat May 6 23:21:20 CDT 2017

[Re-sending with minor edits since this didn't initially go to the list.]

> On May 5, 2017, at 3:25 PM, Tony Allevato via swift-evolution <swift-evolution at swift.org> wrote:
> Hi Tony, this is called out in the proposal :) In addition to the fact that it requires writing boilerplate code manually and updating all references to the deprecated property in type's implementation, there are performance implications as well due to the change in memory management behavior.

To be blunt: Why should we care if a deprecated symbol is slow? It's deprecated, so you shouldn't be using it. (And it's only the public-facing part of it that's slow, which you *really* shouldn't be using.)

Besides, I have a hard time believing we couldn't detect when the getter is just `return otherProperty` and the setter is just `otherProperty = newValue` and optimize it better. 

Sent from my iPad

More information about the swift-evolution mailing list