> > * What is your evaluation of the proposal? My team just started using Swift a few weeks ago. But based on my experience in Objective-C and problems with retain cycles I really really like this proposal. Makes the code easier to grasp because by just reading it I know that that closure cannot escape by default, so the receiver will not hold onto to it for longer than I expect. I totally approve this change. Sounds awesome. > * Is the problem being addressed significant enough to warrant a > change to Swift? Based on my experience using blocks and async callbacks in Objective-C, yes. I expect Swift to be safe by default and this helps solving a common problem for me. > * Does this proposal fit well with the feel and direction of Swift? Yes, safe by default. Without being hard to use. > * If you have used other languages or libraries with a similar > feature, how do you feel that this proposal compares to those? N/A > * How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? I read the proposal.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
