<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 20, 2016, at 12:27 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Maybe I'm not getting something. But if you only want T | U | V to expose members required by common protocols P, Q, and R, since you know the types at compile time, you also know the common protocols. Why wouldn't you just write P & Q & R, and if necessary precondition(x is T || x is U || x is V)?<br class=""></div></blockquote><div><br class=""></div><div>This isn’t something I personally was advocating for (in fact I specifically suggested *not* proposing this would be a better strategy for receiving serious consideration of something union-ish).</div><div><br class=""></div><div>However, if we *did* do something like this it would provide a static verification that the precondition is met while still exposing the members of the common protocol(s) directly. That is substantially better than runtime verification of the precondition or the boilerplate necessary to expose provide forwarding members.</div><div><br class=""></div><div>My personal interest in something union-ish is really along the lines of syntactic sugar for enums.</div><div><br class=""></div><div>Rather than writing this:</div><div><br class=""></div><div>enum StringOrIntOrBool {</div><div> case .string(String)</div><div> case .int(Int)</div><div> case .bool(Bool)</div><div>}</div><div><br class=""></div><div>func foo(values: [StringOrIntOrBool]) {}</div><div><br class=""></div><div>foo([.string(“hello”), .int(42)])</div><div><br class=""></div><div><br class=""></div><div>I would prefer to just write:</div><div><br class=""></div><div>func foo(values: String | Int | Bool) {}</div><div><br class=""></div><div>foo([“hello”, 42])</div><div><br class=""></div><div><br class=""></div><div>The use case for this I found is in designing DSLs of various kinds where you need to accept a heterogenous collection of a specific fixed list of concrete types. The primary concern is to have static verification of the possible values provided by the caller without requiring callers to manually instantiate cases and without polluting the member types with unwanted conformance to a single-use protocol (which would be an alternative if we get sealed protocols).</div><div><br class=""></div><div>If we add automatic lifting as Brent suggested that solves the primary concern I have. If we do add that, introducing the union-like notation would make sense as convenient syntactic sugar for use in these scenarios where the sugar states the intent more clearly and concisely than something a contrived name like `StringOrIntOrBool`. But as I have already stated, that is as secondary concern and automatic lifting alone would solve the primary (call site / library user) concern.</div><div><br class=""></div><div>Matthew</div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_quote"><div dir="ltr" class="">On Sat, Aug 20, 2016 at 12:35 Matthew Johnson <<a href="mailto:matthew@anandabits.com" class="">matthew@anandabits.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
> On Aug 20, 2016, at 10:36 AM, Haravikk <<a href="mailto:swift-evolution@haravikk.me" target="_blank" class="">swift-evolution@haravikk.me</a>> wrote:<br class="">
><br class="">
><br class="">
>> On 19 Aug 2016, at 15:38, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
>><br class="">
>> Ad-hoc enums have been discussed already, at length, and all the weaknesses touched on then still apply now. For instance, since they're ad-hoc, can you pass an instance of type "Int | String" as an argument if the function expects a "String | Int | Float"? Enums don't have duck typing behavior like that; if your ad-hoc type does, then it's not very much like an enum; if it doesn't, it won't feel much like a union type.<br class="">
><br class="">
> While ad-hoc enums are certainly similar I don't think that this problem applies to unions; the problem with ad-hoc enums is that while cases may have the same name, the meaning of a case may not be identical, so compatibility is uncertain. For type unions I'd say this isn't an issue; I'd say that yes, String | Int is compatible with String | Int | Float as every possible value can be carried over (whereas the reverse is not true), they're just values of one of several types, so as long as the conversion is possible, it should be fine to pass it on (or rather, repackage it behind the scenes).<br class="">
><br class="">
>> Moreover, an ad-hoc "String | Int" may look like a union type, but until switching over an instance to cast it, you can't invoke any methods common to String and Int. So it really doesn't feel like a union type at all.<br class="">
><br class="">
> Could it not do that though? I'd say that a union type should conform to any common protocols that its members conform to; if this can be done in the initial release then great, otherwise it can come later.<br class="">
<br class="">
Conforming to common protocols would be much better than an implicit ad-hoc / duck-typed protocol that simply exposes all common members. But there is strong opposition to unions, much of which is related to implementation complexity. It seems to me that the path to having unions or a union-ish feature receiving serious consideration is to demonstrate the value they can offer even with relatively restricted functionality (such as syntactic sugar for enums with implicit lifting). If that is successful we will have an opportunity to work with them and make a case for enhancements in the future.<br class="">
<br class="">
Also, it won't always possible for a union to conform to a protocol conformed to by all member types. If the protocol has `Self` requirements in argument position it would not be able to conform and if it has associated type requirements which are bound to different concrete types in the types making up the union it would also not be able to conform.<br class="">
<br class="">
Matthew</blockquote></div>
</div></blockquote></div><br class=""></body></html>