[swift-evolution] [Pre-Proposal-Discussion] Union Type - Swift 4

[T.J. Usiyan]

These are a couple comments from Chris Lattner that come to mind

"FWIW, this has been discussed before on swift-evolution.  Adding them
isn’t out of the question, but it is a lot more complicated than it looks
for the type checker."

"Here is my concern:  Swift enums should be good enough that we don’t need
an Either type.  If defining your own custom enum is hard or bad, then we
should fix that.

There are a number of concepts floating around that would make enums better
in various ways.  One specific one would be to synthesize optional
accessors that line up with enum cases."
-  in "Either in the Swift Standard Library"


On Wed, Aug 17, 2016 at 7:06 PM, Karl via swift-evolution <
swift-evolution at swift.org> wrote:

>
> On 11 Aug 2016, at 07:18, Chris Lattner via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>
> On Aug 10, 2016, at 8:15 PM, Xiaodi Wu via swift-evolution <
> swift-evolution at swift.org> wrote:
>
> I don't know if the core team feels differently now with respect to Swift
> 4, but union types are listed as a "commonly rejected change":
>
> https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md
>
>
> There is no change in opinion here.  This topic is also out of scope for
> Swift 4 stage 1 in any case.
>
> -Chris
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
> While I appreciate if you don’t want to reply, given the way the tone of
> this discussion seems to have turned:
>
> The section on this topic in the “commonly-proposed” section could use
> some elaborating. On the face of it, it seems like a handy feature, and I’m
> sure many would like to know (now and in the future) why the core-team
> feels this way. Only then can they properly judge when circumstances may
> have changed, and if/when to raise the issue again.
>
> Thanks
>
> Karl
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160817/c429ab4d/attachment.html>