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.
> On Jan 25, 2017, at 12:25 AM, Dave Kliman via swift-evolution > <email@example.com> wrote: > > 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