This Stack Overflow post list several different methods different members of the community have gone
about attacking Scala's lack of native union type:
I understand Scala is intended to be a scala-ble language and enabling users to create powerful
constructs like this on their own is one of the goals of the language. However reading over the Futures SIP got
me to thinking that part of the motivations for having Futures directly in the standard library was to have a
consistent version across the Scala ecosystem. I think that motivation could be applied here as well and with
similar benefits.
I also remember Martin mentioning that union types would eventually be added to the language, but my google-fu
is lacking and I can't dig up the quote. I haven't been keeping up with the mailing list for a while so I am not
sure if this is still the view held by Martin / others in the community.