On 14 Jun 2017, at 23:22, Goffredo Marocchi via swift-evolution <[email protected]> wrote:
>> Yes, I think we are all in vigorous agreement about this. The question is >> whether, at this point in Swift's evolution, a wide-ranging migration due to >> a new required keyword will be well tolerated. If not, then the solution is >> constrained. >> > > I personally vote to accept such a migration at this point, but I am not sure > how others feel. I personally don't want to waste time in migrations if the resulting code is worse, but I think this proposal is very reasonable. It's an improvement and the migration is painless if the fixit applies. And it's a feature that if you were using it, you definitely know what's going on. Also, if this proposal were accepted as is, having to opt-in, I would personally not want it. -- Víctor Pimentel _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
