<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
* What is your evaluation of the proposal?<br></blockquote><div><br></div><div>+1. I believe "pass-through" functions such as autoreleasepool, withExtendedLifetime/withUnsafePointer, dispatch_sync, etc. should all have a generic-result/rethrowing signature.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> * Is the problem being addressed significant enough to warrant a<br>
change to Swift?<br></blockquote><div><br></div><div>Workarounds were doable, but clunky.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* Does this proposal fit well with the feel and direction of<br>
Swift?<br></blockquote><div><br></div><div>Seems so.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* If you have you used other languages or libraries with a<br>
similar feature, how do you feel that this proposal compares<br>
to those?<br></blockquote><div><br></div><div>N/A</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* How much effort did you put into your review? A glance, a<br>
quick reading, or an in-depth study?<br></blockquote><div><br></div><div>Quick reading of the proposal, because the implementation is very simple, and I've implemented similar utility functions before.</div><div><br></div><div><br></div><div>Jacob</div></div></div></div>