<div dir="ltr">Oh, this is a really interesting use case for that protocol. I wonder if RawRepresentable might one day be auto-derivable for certain types, as part of a more comprehensive Swift serialization/deserialization feature.<div><br></div><div>Austin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 1:05 PM, Brent Royal-Gordon via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> On the other hand: What's the point of "raw-value enums"? Are they just a bridge-technogy, or is it ok to use them to store constants?<br>
<br>
</span>I think of RawRepresentable (the protocol behind rawValue) as a serialization mechanism, basically the Swift standard library's answer to NSCoding. Thus, rawValue is a way to serialize your enum into an Int or String you know how to read and write from disk. More broadly, I often apply RawRepresentable to structs and have them return plist- or JSON-compatible dictionaries.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Brent Royal-Gordon<br>
Architechies<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<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/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div>