<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><blockquote type="cite"><div><span> * What is your evaluation of the proposal?</span><br></div></blockquote><div>Plus one. Open is my keyword of choice. </div><div><br></div><blockquote type="cite"><div><span> * Is the problem being addressed significant enough to warrant a change to Swift?</span><br></div></blockquote><div><br></div><div>Yes. But I think some sort of patch ability should be introduced as a compromised. </div><div><a href="http://article.gmane.org/gmane.comp.lang.swift.evolution/1805/match=patch+sealed">http://article.gmane.org/gmane.comp.lang.swift.evolution/1805/match=patch+sealed</a></div><div><br></div><div>Perhaps a way to have an extension on a sealed class to be marked as a patch that is able to hook up to the willSet/didSet on a sealed property or be able to run before or after a method function. I think something like this could ease the pain of a completely closed to patching system. </div><br><blockquote type="cite"><div><span> * Does this proposal fit well with the feel and direction of Swift?</span><br></div></blockquote>Yes. <br><blockquote type="cite"><div><span> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span><br><span> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br></div></blockquote><div><br></div>Moderate effort. <br><blockquote type="cite"><div><span></span><br></div></blockquote></body></html>