> On Feb 17, 2017, at 3:18 PM, Douglas Gregor <dgre...@apple.com> wrote: > > https://github.com/apple/swift-evolution/blob/master/proposals/0153-compensate-for-the-inconsistency-of-nscopyings-behaviour.md > > • What is your evaluation of the proposal?
I think a warning is very appropriate. However, occasionally a constructor might be non-copying on purpose, so we'll need a way to disable the warning. A few possibilities: * Use .self on the value * Parenthesize the value * Parenthesize the variable I don't favor using compiler magic. Too spooky. > • Is the problem being addressed significant enough to warrant a change > to Swift? Yeah, that's a pretty easy mistake to make. > • Does this proposal fit well with the feel and direction of Swift? Yes. Swift usually tries to help you avoid mistakes. > • If you have used other languages or libraries with a similar feature, > how do you feel that this proposal compares to those? N/A. > • How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? Quick reading. -- Brent Royal-Gordon Architechies _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
