<div dir="ltr">Since it’s still common to see prefixes in use in Objective-C, I wonder if we could add that with a new attribute:<div><br></div><div><font face="monospace, monospace">@objcprefix(JRK) enum City: String {</font></div><div><font face="monospace, monospace"><span class="Apple-tab-span" style="white-space:pre">        </span>case NewYork = &quot;New York&quot;</font></div><div><font face="monospace, monospace">}</font></div><div><br></div><div>Would then appear in Objective-C as:</div><div><br></div><div><font face="monospace, monospace">typedef NSString * JRKCity;</font></div><div><font face="monospace, monospace">static JRKCity const JRKCityNewYork = @&quot;New York&quot;;</font></div><div><br></div><div>It’s a minor tweak, but would help especially with mixed-language source code where the Objective-C code is still prefixed.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica">Jeff Kelley</div><div style="font-family:Helvetica"><br></div><div style="font-family:Helvetica"><a href="mailto:SlaunchaMan@gmail.com" style="color:rgb(17,85,204)" target="_blank">SlaunchaMan@gmail.com</a> | <a href="https://twitter.com/SlaunchaMan" style="color:rgb(17,85,204)" target="_blank">@SlaunchaMan</a> | <a href="http://jeffkelley.org/" style="color:rgb(17,85,204)" target="_blank">jeffkelley.org</a></div></div></div></div>
<br><div class="gmail_quote">On Wed, Jan 4, 2017 at 5:51 PM, Derrick Ho via swift-evolution <span dir="ltr">&lt;<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The underline can be omitted. To remain more consistent.  <br><span class=""><br>    enum City: String {<br>       case NewYork = &quot;New York&quot;<br>    } <br><br></span>    typedef NSString * City;<br>    static City const CityNewYork = @&quot;New York&quot;;<div class="HOEnZb"><div class="h5"><br><br><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 4, 2017 at 2:22 PM Rod Brown &lt;<a href="mailto:rodney.brown6@icloud.com" target="_blank">rodney.brown6@icloud.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class="m_726753818258568081gmail_msg"><div class="m_726753818258568081gmail_msg">I&#39;m not part of the core team, of course, but I like this change in principle.</div><div id="m_726753818258568081m_1459424563651473008AppleMailSignature" class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg"></div><div id="m_726753818258568081m_1459424563651473008AppleMailSignature" class="m_726753818258568081gmail_msg">My one concern in this case would be choosing a naming convention for the back port that makes sense both ways. The naming convention you propose ( EnumName_EnumCase) seems inconsistent with the current import of strings from Obj-C to Swift. Could we find a way to unify them?</div></div><div dir="auto" class="m_726753818258568081gmail_msg"><div class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg">On 31 Dec 2016, at 4:15 am, Derrick Ho via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="m_726753818258568081gmail_msg" target="_blank">swift-evolution@swift.org</a>&gt; wrote:<br class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg"></div><blockquote type="cite" class="m_726753818258568081gmail_msg"><div class="m_726753818258568081gmail_msg">I&#39;m trying to revive an old thread.  I&#39;d like to hear from the community.<br class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg">Can we make a swift enum string interoperable with Objective-C?<br class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg">Currently NS_STRING_ENUM ports from objective-c to swift but not the other way around.<br class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg">I feel that if you can go one direction you should be able to go back.<br class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg">@objc<br class="m_726753818258568081gmail_msg">enum City: String {<br class="m_726753818258568081gmail_msg">       case NewYork = &quot;New York&quot;<br class="m_726753818258568081gmail_msg">} <br class="m_726753818258568081gmail_msg"><br class="m_726753818258568081gmail_msg">Make this available as a global string in objective -c ?<br class="m_726753818258568081gmail_msg"><div class="gmail_quote m_726753818258568081gmail_msg"><div dir="ltr" class="m_726753818258568081gmail_msg">On Wed, Nov 23, 2016 at 5:55 AM Derrick Ho &lt;<a href="mailto:wh1pch81n@gmail.com" class="m_726753818258568081gmail_msg" target="_blank">wh1pch81n@gmail.com</a>&gt; wrote:<br class="m_726753818258568081gmail_msg"></div><blockquote class="gmail_quote m_726753818258568081gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="white-space:pre-wrap" class="m_726753818258568081gmail_msg">I think enum strings should gain better interoperability with swift. Something like this:

    enum City: String {
       case NewYork = &quot;New York&quot;
    } 

This can be ported over to Objective-c like this:

    typedef NSString * City;
    static City const City_NewYork = @&quot;New York&quot;;<br class="m_726753818258568081gmail_msg"></div>
</blockquote></div>
</div></blockquote></div><div dir="auto" class="m_726753818258568081gmail_msg"><blockquote type="cite" class="m_726753818258568081gmail_msg"><div class="m_726753818258568081gmail_msg"><span class="m_726753818258568081gmail_msg">______________________________<wbr>_________________</span><br class="m_726753818258568081gmail_msg"><span class="m_726753818258568081gmail_msg">swift-evolution mailing list</span><br class="m_726753818258568081gmail_msg"><span class="m_726753818258568081gmail_msg"><a href="mailto:swift-evolution@swift.org" class="m_726753818258568081gmail_msg" target="_blank">swift-evolution@swift.org</a></span><br class="m_726753818258568081gmail_msg"><span class="m_726753818258568081gmail_msg"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="m_726753818258568081gmail_msg" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a></span><br class="m_726753818258568081gmail_msg"></div></blockquote></div></blockquote></div>
</div></div><br>______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br></blockquote></div><br></div></div>