<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div><br><br>Enviado desde mi iPhone</div>El 4 abr 2017, a las 22:04, Douglas Gregor <<a href="mailto:dgregor@apple.com">dgregor@apple.com</a>> escribió:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 4, 2017, at 12:31 PM, Víctor Pimentel Rodríguez via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">Sorry to be late :/<br class=""><div class="gmail_quote"><br class=""></div><div class="gmail_quote">On Fri, Mar 31, 2017 at 5:29 PM, Chris Lattner via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">* What is your evaluation of the proposal?</div></blockquote><div class=""><br class=""></div><div class="">More positive than the first one, but still some rough edges.</div><div class=""><br class=""></div><div class="">One concern that I still have is that if we use @objcMembers, @nonobjc methods/properties are going to be even trickier to find.</div><div class=""><br class=""></div><div class="">If such modifier existed, I would like the compiler to warn me of public methods/properties that cannot be bridged to ObjC, because I have explicitly told the compiler that I want this object to live in the ObjC runtime. Of course, with a fixit recommending something like explicitly using @nonobjc.</div></div></div></div></div></blockquote><div><br class=""></div>@objc on extensions behaves this way; the compiler will produce an error if the entity cannot be exposed to Objective-C.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div></div></blockquote><div><br></div><div>Yeah, I think you explained the behavior of extensions very well in the proposal:</div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">> If some member within that extension cannot be exposed to Objective-C, such as <code style="box-sizing: border-box; padding: 0.2em 0px; margin: 0px; border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px;">SwiftClass.bar()</code>, the compiler will produce an error.</span></div><div><br></div><div>My specific question was about implicitly @nonobjc members in a @objcMembers class. That is, would the compiler allow such member with no @nonobjc annotation? And would extensions of such classes allow those members? Do I need to put @objc in every extension of a @objcMembers class to get that compiler error?</div><div><br></div><div>By the way, I very much appreciate the level of care that you put into this proposal and its implementation. Thank you very much!</div><br><div>--</div><div>Víctor Pimentel</div></body></html>