Is the status quo in this honey moon phase better? Sent from my iPhone
> On 19 May 2016, at 19:12, Sean Heber via swift-evolution > <[email protected]> wrote: > > I think it is too easy to just add warnings for warts and call it a day. > These problems, IMO, should be addressed somehow eventually - but not with a > warning. Either Swift decides these situations are errors and refuses to > enable them at all, or the constructs involved should be carefully > reconsidered and changed to prevent them from even happening or being > encouraged in the first place. > > So in short: I too do not agree to adding optional warnings. :) > > l8r > Sean > > >> On May 19, 2016, at 12:58 PM, David Waite via swift-evolution >> <[email protected]> wrote: >> >> I believe the Swift Team has previously stated they do not want opt-in >> warnings defining alternate swift ‘grammars’. I don’t believe there are any >> existing -W flags for the compiler, for instance. >> >> If there is shadowing warning added, I’m of the opinion it should work >> similar to the override keyword. >> >> -DW >> >>> On May 19, 2016, at 11:28 AM, Vladimir.S via swift-evolution >>> <[email protected]> wrote: >>> >>> On 18.05.2016 22:43, Krystof Vasa wrote: >>>> I agree that shadowing variables is not a good idea, but I stand by my >>>> point that it's potentially dangerous and error-prone to allow accessing >>>> instance variables without `self`. >>> >>> Could we all agree that we need these options: >>> 1. option to turn on warnings on accessing instance variables without `self` >>> 2. option to turn on warnings on shadowing >>> And that by default, none of that options should be enabled. >>> ? >>> _______________________________________________ >>> 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
