<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>So, to be clear, a warning about making internal variables more private based on their usage in the entire module? </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Sounds doable. Probably wouldn't need to go through evolution to get it too (but I'll let others make that call). Please file an SR about this too.<br><br>~Robert Widmann</div><div><br>2017/01/25 3:25、Dave Kliman via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> のメッセージ:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">Hi!<div class=""><br class=""></div><div class="">I’m somewhat new to swift, so this issue may have been covered.</div><div class=""><br class=""></div><div class="">I really like how I get a warning for variables I’ve declared, but have not mutated, or constants that I did not read.</div><div class=""><br class=""></div><div class="">What about warnings for anything not accessed outside its declared scope, encouraging the use of <i class="">private</i>, or <i class="">fileprivate</i> more often?</div><div class=""><br class=""></div><div class="">-Dave</div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>