So, to be clear, a warning about making internal variables more private based on their usage in the entire module?
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. ~Robert Widmann 2017/01/25 3:25、Dave Kliman via swift-evolution <email@example.com> のメッセージ: > Hi! > > I’m somewhat new to swift, so this issue may have been covered. > > I really like how I get a warning for variables I’ve declared, but have not > mutated, or constants that I did not read. > > What about warnings for anything not accessed outside its declared scope, > encouraging the use of private, or fileprivate more often? > > -Dave > _______________________________________________ > swift-evolution mailing list > firstname.lastname@example.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list email@example.com https://lists.swift.org/mailman/listinfo/swift-evolution