compiler bug?pic.twitter.com/P8dehnwcx1
-
I forget what I was doing but I think B was a type param (not specialised) so truely it's Any :> B :> Null. But also isn't Int with AnyRef => Integer? AnyRef with Nothing sounds insane/uninhabited, so shouldn't "ex falso quodlibet" follow? Don't know how these extremes combine.
There's nothing which says that a (non-specialized) type param has to be :> Null, because there's also nothing which requires that that type param is used as the type of a value. It could just be used to resolve an implicit or as a bound.
-
-
A type, Int with AnyRef, would have all the properties of http://scala.Int and all the properties of AnyRef, if it were to exist (which it can't) but that doesn't stop the type existing, for example as the GLB of Int and AnyRef.
-
AnyRef with Nothing is just Nothing, because *everything* is a supertype of Nothing, so Nothing subsumes the type AnyRef (and AnyVal and Null).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.