-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Array of Parametric Typed data fails Type Equality (but passes Type Identity) #11243
Labels
domain:types and dispatch
Types, subtyping and method dispatch
kind:bug
Indicates an unexpected problem or unintended behavior
kind:regression
Regression in behavior compared to a previous version
Comments
Futher:
as well as:
|
Persistes with no change if the subtypes are made concrete:
Infact it persists even if the constraint is removed entirely:
What does work is:
|
I can confirm that all works as expect in v"0.3.9-pre+12" |
oxinabox
changed the title
Array of Parametric Typed data fails Type Equality (but Passed Type Identity)
Array of Parametric Typed data fails Type Equality (but passes Type Identity)
May 12, 2015
vtjnash
added
the
kind:bug
Indicates an unexpected problem or unintended behavior
label
May 12, 2015
simonster
added
domain:types and dispatch
Types, subtyping and method dispatch
kind:regression
Regression in behavior compared to a previous version
labels
May 13, 2015
mbauman
pushed a commit
to mbauman/julia
that referenced
this issue
Jun 6, 2015
looks like I had tried to add a clause to jl_subtype_le that wasn't present in 0.3. failed experiment I guess.
tkelman
pushed a commit
to tkelman/julia
that referenced
this issue
Jun 6, 2015
looks like I had tried to add a clause to jl_subtype_le that wasn't present in 0.3. failed experiment I guess.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
domain:types and dispatch
Types, subtyping and method dispatch
kind:bug
Indicates an unexpected problem or unintended behavior
kind:regression
Regression in behavior compared to a previous version
On version: v"0.4.0-dev+4770"
I have made the MWE to illustrate:
Comments are the printed output of that/the preceeding line
Define the type:
create a Vector of it:
Check its equality:
That doesn't seem right at all.
How can they be Identical (
===
), but not Equal (==
)?Further, this breaks function calls:
The text was updated successfully, but these errors were encountered: