3 ms·
In Swift 2.2 they're going to add warnings but they won't break previous versions of source (yet). In Swift 3.0 they'll remove the deprecated syntaxes.
by ash_gti 11y ago
In Swift 2.2 they're going to add warnings but they won't break previous versions of source (yet).
In Swift 3.0 they'll remove the deprecated syntaxes.
- brudgers 11y agoThat's a fair point. In practice, it doesn't mean any less work, just longer to rewrite offending code...or not to. Deprecation still imposes debt.
- Tloewald 11y agoNon deprecation also imposes debt. So does stagnation. So you pick your poison.
- Jtsummers 11y agoBetter than the debt of a changed language/library that allows for multiple and confusing variations thanks to not removing those features (syntax, keywords, functions). It makes looking at old documentation difficult (it's wrong now), but also means that outdated guides aren't still correct (so they'll get culled or corrected more quickly) and we won't have the OpenGL situation.