[swift-evolution] warnings for out of scope?

Michael Ilseman milseman at apple.com
Thu Jan 26 14:21:25 CST 2017

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 <swift-evolution at swift.org> 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
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170126/380b9b19/attachment.html>

More information about the swift-evolution mailing list