<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><blockquote type="cite"><div> </div>
<div>* What is your evaluation of the proposal?<br></div>
</blockquote><div style="font-family:Arial;">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.<br></div>
<div style="font-family:Arial;"> </div>
<div style="font-family:Arial;">I totally approve this change. Sounds awesome.<br></div>
<div style="font-family:Arial;"> </div>
<blockquote type="cite"><div>* Is the problem being addressed significant enough to warrant a change to Swift?<br></div>
</blockquote><div style="font-family:Arial;">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.<br></div>
<div style="font-family:Arial;"> </div>
<blockquote type="cite"><div>* Does this proposal fit well with the feel and direction of Swift?<br></div>
</blockquote><div style="font-family:Arial;">Yes, safe by default. Without being hard to use.<br></div>
<div style="font-family:Arial;"> </div>
<blockquote type="cite"><div>* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div>
</blockquote><div style="font-family:Arial;">N/A<br></div>
<div style="font-family:Arial;"> </div>
<blockquote type="cite"><div>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div>
</blockquote><div style="font-family:Arial;">I read the proposal.</div>
</body>
</html>