On Thu, Jun 16, 2016 at 11:39 AM, L. Mihalkovic via swift-evolution < [email protected]> wrote:
> Likely a lint level feature, no? Agreed. Sounds like a linter feature. > > On Jun 16, 2016, at 6:27 PM, Sean Heber via swift-evolution < > [email protected]> wrote: > > > > I would think this would not apply to public classes. > > > > There has also been discussion in the past about making final the > default - I don’t remember if that ever resolved into some kind of > consensus or not, though. > > > > l8r > > Sean > > > > > >> On Jun 16, 2016, at 11:23 AM, Saagar Jha via swift-evolution < > [email protected]> wrote: > >> > >> Correct me if I’m wrong, but if you’re writing some kind of framework > and your class is not final but never subclassed, you wouldn’t want the > warning, even if you’d like to allow users to subclass it? > >> > >> > >> > >> On Thu, Jun 16, 2016 at 9:02 AM Rehat Kathuria via swift-evolution < > [email protected]> wrote: > >> I’d like the compiler to present a warning when a class not declared as > final is never subclassed. Thoughts? > >> _______________________________________________ > >> swift-evolution mailing list > >> [email protected] > >> https://lists.swift.org/mailman/listinfo/swift-evolution > >> -- > >> -Saagar Jha > >> _______________________________________________ > >> swift-evolution mailing list > >> [email protected] > >> https://lists.swift.org/mailman/listinfo/swift-evolution > > > > _______________________________________________ > > swift-evolution mailing list > > [email protected] > > https://lists.swift.org/mailman/listinfo/swift-evolution > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
