<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Addressing a few common themes:</div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class="">Imported code from other languages should not be warn unused. That is not the assumption the code was developed under, and Swift should not be held to that contract.</li><li class="">Imported code from Cocoa should not be warn unused because a full audit is impractical. </li></ul></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><br class=""></div><div class=""> It seems to me that if you create a UIView(frame: rect) for example and discard the result, that is typically more error-y than intentional. On the other hand, many Boolean results and oserr results are reasonably ignorable. As for the <span style="font-family: Palatino-Roman;" class="">popViewController methods on UINavigationController, whose results are typically ignored, I'm wavering between "yes, that should raise a warning" and "yes, that method should be audited and marked as disposable".</span></div><div class=""><span style="font-family: Palatino-Roman;" class=""><br class=""></span></div><div class="">This is one of those areas where I would prefer advice and feedback from the Core Team before modifying the proposal.</div><div class=""><br class=""></div></blockquote><div class=""><ul class="MailOutline"><li class="">This will confuse people who do not read release notes or the documentation, and they will use the less advantageous "let _ =" instead.</li><li class="">"This doesn't mesh with my personal coding style"</li><li class="">"I'm already a careful developer and my code would not benefit"</li><li class="">All my code has been thoroughly pre-audited and the transition will be painful.</li></ul><div class=""><br class=""></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">If adopted, this proposal will incur negative costs for some developers. I believe the benefits for the language and the wider community outweigh the negatives.</blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><br class=""></blockquote><ul class="MailOutline"><li class="">This isn't fluent interface-friendly</li></ul><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><i class=""><br class=""></i>This one confuses me as I was under the impression that method chaining consumes each result in turn, so won't cause warnings.<br class=""><blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;" class=""><div class=""><br class=""></div></blockquote></blockquote><div class=""><ul class="MailOutline"><li class="">There isn't an "Impact on existing code" section.</li></ul></div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">Adrian and I need to add that. At a minimum:</div><div class=""><br class=""></div><div class="">- The migrator should remove existing @warn_unused_results in Swift code</div><div class="">- The section should state how code imported from other languages (particularly C-based and Cocoa) will be treated. I want advice from the Core Team on how they think this will be best addressed before I add that to the proposal.</div></blockquote><div class=""><br class=""></div></body></html>