4 ms·
Looks like two potentially breaking changes at source level: https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.m
by brudgers 11y ago
Looks like two potentially breaking changes at source level:
https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md https://github.com/apple/swift-evolution/blob/master/proposa...
https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md https://github.com/apple/swift-evolution/blob/master/proposa...
- Alphasite_ 11y agoAre those not going to be marked depecrated and broken in swift 3?
- ash_gti 11y agoIn 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.
- alblue 11y agoDon't forget the removal of the C-style for loop, along with the increment ++ and decrement -- operators. https://github.com/apple/swift-evolution/blob/master/proposals/0007-remove-c-style-for-loops.md https://github.com/apple/swift-evolution/blob/master/proposa... https://github.com/apple/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md https://github.com/apple/swift-evolution/blob/master/proposa...
- brudgers 11y agoThe one's I linked to are listed as changes incorporated into Swift 2.2 per the announcement.
- whiddershins 11y agoI am baffled by the for loop removal thing. I just spent a while reading about both stride and for ... in, and I feel like there are any number of cases where I would rather use a C-style for loop.
- xxpor 11y agoI'm not familiar with swift, but Python doesn't have C style for loops either. People just write: for i in range(10): instead.
- vram22 11y agoMore generally, people write: for item in sequence: which is somewhat general (sequences include lists, dicts, strings, tuples, generators, text files and more [2]), and it covers a wide range [1] of use cases. [1] Pun not intended. [2] Basically, any iterable. This include custom iterables you can define, which can then be iterated over using the same standard for loop. A unifying feature of the language: "The use of iterators pervades and unifies Python." https://docs.python.org/2/tutorial/classes.html#iterators https://docs.python.org/2/tutorial/classes.html#iterators
- rat87 11y agowhat sort of cases? Could you use a while loop instead? I feel like (as long as the numerical case optimizes to the same thing) the for-in loop (and occasional use of the while loop) is clearer.
- Sephiroth87 11y agoChanges like this are usually converted automatically by the Xcode migration tool...