<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">This seems best handled as a lint rule, probably filed under “pedantic”. It makes sense to apply to a project at certain milestones, but could be noisy during incremental development.</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 25, 2017, at 12:25 AM, Dave Kliman via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>