<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 14 Oct 2016, at 19:56, Haravikk <<a href="mailto:swift-evolution@haravikk.me" class="">swift-evolution@haravikk.me</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Huh, see, that's why I posted the thread; I didn't know you could do it that way (I've been trying the RawRepresentable part as its own type).</div><div class="">In that case yes, it seems like all that's need is an expansion of what's allowable on the rhs of raw value enum cases.</div><br class=""></div></div></blockquote><div><br class=""></div><div>And that’s why I come here - to share the little bits that I’ve learned :)</div><div><br class=""></div><div>I think a lot of people have misconceptions about what RawRep is, and the inheritance syntax for enums doesn’t much help that. It doesn’t affect the storage or layout of the enum whatsoever; it’s just a protocol conformance. The compiler generates these same kind of switch statements, and that’s really the only reason AFAIK that we have the limitations (e.g. int/string literal) that we do.</div><div><br class=""></div><div>There are no restrictions on what can be RawRepresentable (structs and classes can also conform), and no limitation on the type of RawType (can also be a struct or a class). You just need to implement it yourself in those cases; I’m guessing because there are complex edge-cases which we don’t want hidden away in a location you can’t easily debug.</div><div><br class=""></div><div>Tuples of Ints and Strings, however, seem like they could easily be supported. For example, we could check that there are no overlapping cases.</div><div><br class=""></div><div>- Karl</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="">On 14 Oct 2016, at 18:11, Karl Wagner <<a href="mailto:razielim@gmail.com" class="">razielim@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class=""><div style="direction: inherit;" class="">Example:</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class=""><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">enum something {</div><div style="direction: inherit;" class=""> case onething</div><div style="direction: inherit;" class=""> case anotherthing</div><div style="direction: inherit;" class="">}</div><div style="direction: inherit;" class="">extension something : RawRepresentable {</div><div style="direction: inherit;" class=""> typealias RawValue = (Int, Int)</div><div style="direction: inherit;" class=""> </div><div style="direction: inherit;" class=""> init?(rawValue: something.RawValue) {</div><div style="direction: inherit;" class=""> switch rawValue {</div><div style="direction: inherit;" class=""> case (1, 1):</div><div style="direction: inherit;" class=""> self = .onething </div><div style="direction: inherit;" class=""> case (2, _):</div><div style="direction: inherit;" class=""> self = .anotherthing</div><div style="direction: inherit;" class=""> default:</div><div style="direction: inherit;" class=""> return nil </div><div style="direction: inherit;" class=""> }</div><div style="direction: inherit;" class=""> }</div><div style="direction: inherit;" class=""> </div><div style="direction: inherit;" class=""> var rawValue: (Int, Int) {</div><div style="direction: inherit;" class=""> switch self {</div><div style="direction: inherit;" class=""> case .onething: return (1, 1)</div><div style="direction: inherit;" class=""> case .anotherthing: return (2, 0)</div><div style="direction: inherit;" class=""> }</div><div style="direction: inherit;" class=""> }</div><div style="direction: inherit;" class="">}</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">let whatisit = something(rawValue: (1, 1))</div><div style="direction: inherit;" class="">something.onething.rawValue</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">Karl</div></div><br class="">Sent from my iPad</div><div class=""><br class="">On 14 Oct 2016, at 19:04, Karl Wagner <<a href="mailto:razielim@gmail.com" class="">razielim@gmail.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div class=""><div style="direction: inherit;" class="">You can already do this; you just need to implement RawRep manually.</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">What I think you mean to propose is that the compiler shorthand we have (which synthesises the conformance if you use the equal signs next to the cases) be extended to support tuples of the types it currently supports. That's a relatively simple, non-source-breaking additive change. It likely doesn't fit in the scope of swift 4 phase 1, though (sorry, I've been guilty of chatting about non-abi stuff too as I encounter things which irritate me; trying to be more disciplined)</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">Karl</div><div style="direction: inherit;" class=""><br class=""></div>Sent from my iPad</div><div class=""><br class="">On 14 Oct 2016, at 12:55, Haravikk via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><span class=""></span><br class=""><blockquote type="cite" class=""><span class="">On 14 Oct 2016, at 09:49, David Sweeris <<a href="mailto:davesweeris@mac.com" class="">davesweeris@mac.com</a>> wrote:</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">I'm very much in favor of the functionality, but I don't think the implementation should rely on compiler magic.</span><br class=""></blockquote><blockquote type="cite" class=""><span class=""></span><br class=""></blockquote><blockquote type="cite" class=""><span class="">- Dave Sweeris </span><br class=""></blockquote><span class=""></span><br class=""><span class="">Well it's not too much in the way of magic really, more just that we need Swift to see tuples as conforming to RawRepresentable and ExpressableAsTuple, although they currently aren't types in the normal sense. So the protocols being used will be the same as you might use yourself, they'll just be applied automatically for tuples.</span><br class=""><span class=""></span><br class=""><span class="">It'd be neat if it could be done properly, but that could involve even more work, but doing this automatically for now should be fairly simple (though I say that as a person who wouldn't be the one doing it ;)</span><br class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote></div></blockquote></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></body></html>