-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error on assignment of assignment expression to variable of type Anything #1917
Comments
Typical example of @gavinking implementing something and forgetting to open an issue here about it ;) |
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
…ng rules for assignment now Otherwise we get things like Type x = (Type) let( Object tmpvar = nothing; y = tmpvar; // here we need to add the (Type) cast as well ) returning tmpvar; for Type x, y; x = y = nothing
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
Because otherwise the Java bottom type is stored in java.lang.Object, which is not of the bottom type, so x = y = null will fail because null is stored in java.lang.Object and can't be assigned to either y or x
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
I give up on trying to fix this totally unnecessary cast, because it has to do with another bug related to rawness of tuple types where we consider that they are raw without considering the fact that in fact they are erased to Sequential, which has far less constraints and rawness
FroMage
added a commit
that referenced
this issue
Nov 19, 2014
There you go, as you can see it was a piece of cake ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relating to ceylon/ceylon-spec#438 and ceylon/ceylon-spec@ad195d3
Anything
probably doesn't make sense here that often, but it looks like a bug nevertheless. FWIW, the use case involved using a marker object formemo
's initial value, to distinguish from a Null result, and eventually doingassert(is Result ...)
, making the type largely irrelevant.The text was updated successfully, but these errors were encountered: