You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
[@gavinking] We could add some reasoning around types like Comparable<Anything> which are empty due to the self type constraint. Perhaps just say that Nothing covers Comparable<Anything>, since I'm not sure if saying Comparable<Anything> is exactly Nothing would be decidable.
These case is distinguishable because:
the type parameter is a self type and is not covariant, and
the type argument does not inherit the type (and is not marked out).
[@RossTate] Is this practical? If I recall, the analysis you ran a while ago showed that no one uses self types in ways that would be relevant to this optimization.
[@gavinking] Not sure if it's useful or not. But after looking at the code, there is no really obvious place to incorporate this reasoning without complicating the algorithms. So: not for 1.2.
[@gavinking] We could add some reasoning around types like
Comparable<Anything>
which are empty due to the self type constraint. Perhaps just say thatNothing
coversComparable<Anything>
, since I'm not sure if sayingComparable<Anything>
is exactlyNothing
would be decidable.These case is distinguishable because:
out
).[Migrated from ceylon/ceylon-spec#1383]
The text was updated successfully, but these errors were encountered: