on Thu Apr 21 2016, Jeremy Pereira <[email protected]> wrote:
>> On 20 Apr 2016, at 19:24, Dave Abrahams via swift-evolution >> <[email protected]> wrote: >> >> >> on Wed Apr 20 2016, Tino Heth <[email protected]> wrote: >> >>> Increment/decrement operators, currying, tuple splat and even the >>> C-style for loop have already been deprecated, and although I would >>> have preferred to keep some of those constructs, I think it is good >>> how progressive Swift is pushed forward ("would we add this feature >>> now if it wasn't already there?"). >> >> We're in a stage of Swift's development where we can ask this question >> fairly freely, > > I think we are already past that stage, whether we like it or > not. There is already quite a lot of Swift code in “production” and > some people in the wider community are already resenting some of the > removals. That may be so, but we are explicitly giving ourselves license to ask these kinds of questions now because we expect it to become much harder in the future. -- Dave _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
