<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div style="font-family:Arial;">> What is your evaluation of the proposal?<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">Very strong -1. Drew has said it all.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">A few extra points:</div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">* If you split a class into a bunch of extensions, chances are it's a large class, and fileprivate keyword provides crucial <b>documentation</b> on which methods and fields are accessed from outside the scope. Even if someone blindly uses private until compiler complains, then switches to fileprivate without thinking, there's still value when reading the code. (This has been mentioned as one of the points against scoped private.)<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">* Encapsulation is in the spirit of Swift's safety goals, we want to encourage it.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">* // MARK is perfectly fine for tightly-coupled class bodies, so if you find yourself using tons of fileprivate, consider switching to a single body with marks<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">* I really like the point that we should uphold the original decision unless we find new compelling arguments that were not considered initially.</div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">> Is the problem being addressed significant enough to warrant a change to Swift?<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">No. I haven't personally seen any complains about this feature in my circles; everyone is happy about tighter access controls.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">> Does this proposal fit well with the feel and direction of Swift?<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">It feels actively against the safety and readability goals of Swift.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">This has been beaten to death in the original proposal.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">Thorough reading of the first half of this discussion, and active participation in the original discussion (as well as writing and shipping lots of Swift code since Swift 0.x).<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">A.<br></div>
<div style="font-family:Arial;"><br></div>
</body>
</html>