<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>+1 one to the updated proposal. I like the change a lot, even if it's even more pain for the poor framework teams. ;-)<br></div>
<div> </div>
<div>Apropos of nothing, a coworker reminded me today of something that would fit well into this proposal, even if only as a clarifying example: UTIs are a great instance of "strongly-typedef'ed strings", with the possibility of user-defined cases, and whose use in Cocoa APIs is often ambiguous. There are several hundred constants, too, so it'd be a good stress-test for everything in the proposal.<br></div>
<div> </div>
<div id="sig40804545"><div class="signature">Cheers!</div>
<div class="signature">Zachary Waldowski<br></div>
<div class="signature"><a href="mailto:zach@waldowski.me">zach@waldowski.me</a><br></div>
</div>
<div> </div>
<div> </div>
<div>On Fri, Jan 22, 2016, at 04:14 PM, Jeff Kelley via swift-evolution wrote:<br></div>
<blockquote type="cite"><div>I have updated <a href="https://github.com/SlaunchaMan/swift-evolution/blob/import-objc-constants/proposals/0000-import-objc-constants.md">the proposal</a> to use struct over enum (<a href="https://github.com/SlaunchaMan/swift-evolution/blob/import-objc-constants/proposals/0000-import-objc-constants.md">https://github.com/SlaunchaMan/swift-evolution/blob/import-objc-constants/proposals/0000-import-objc-constants.md</a>).<br></div>
<div> </div>
<div><blockquote type="cite"><div>On Jan 20, 2016, at 11:01 PM, Douglas Gregor <<a href="mailto:dgregor@apple.com">dgregor@apple.com</a>> wrote:<br></div>
<div> </div>
<div><div style="font-family:HelveticaNeue;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-position:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;orphans:auto;text-align:start;text-indent:0px;text-transform:none;white-space:normal;widows:auto;word-spacing:0px;-webkit-text-stroke-width:0px;"><div>FWIW, I suggest that you put “String” somewhere in the title of your proposal when you revise it.<br></div>
</div>
</div>
</blockquote><div> </div>
</div>
<div>Would this need to be limited to strings? There are other “magic constants” that could conceivably be imported as structs—I’m thinking, for instance, error codes.<br></div>
<div> </div>
<div> </div>
<div><div><span class="font" style="font-family:Helvetica">Jeff Kelley</span><br></div>
<div><div style="font-family:Helvetica;line-height:normal;orphans:2;text-align:-webkit-auto;widows:2;word-wrap:break-word;-webkit-line-break:after-white-space;"><div style="line-height:normal;text-align:-webkit-auto;word-wrap:break-word;-webkit-line-break:after-white-space;"><div style="line-height:normal;text-align:-webkit-auto;word-wrap:break-word;-webkit-line-break:after-white-space;"><div> </div>
<div style="word-wrap:break-word;-webkit-line-break:after-white-space;"><div> </div>
<div><span style="border-collapse:separate;line-height:normal;-webkit-border-horizontal-spacing:0px;-webkit-border-vertical-spacing:0px;"><a href="mailto:SlaunchaMan@gmail.com">SlaunchaMan@gmail.com</a> | <a href="https://twitter.com/SlaunchaMan">@SlaunchaMan</a> | <a href="http://jeffkelley.org">jeffkelley.org</a></span><br></div>
</div>
<div> </div>
</div>
</div>
</div>
</div>
<div><blockquote type="cite"><br></blockquote></div>
</div>
<div><u>_______________________________________________</u><br></div>
<div>swift-evolution mailing list<br></div>
<div><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br></div>
<div><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div>
</blockquote><div> </div>
</body>
</html>