Damn, there seems to be no better way to create reactions than saying something 
stupid ;-) - to bad the reactions tend to focus on the stupidity in this case...
It should have been "union" instead of "sum", so basically having Optional<T> 
modeled as (T | Void)

> Enums in Swift *are* sum types. There are various ergonomic issues with their 
> usability, perhaps, but any implementation of sum types would be different 
> sugar over the same underlying semantic model.

_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to