-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
convert to non-varargs Tuple ignores trailing element mismatch #17198
Comments
Worked in 0.4. This is absurd. |
Reduction:
Though interestingly |
More reduced: julia> typeintersect(Type{Tuple}, Type{Tuple{}})
Type{Tuple{}} and julia> Type{Tuple{}} <: Type{Tuple}
true |
This issue seems familiar. Did we something related before? |
Just from knowing the code that implements this, I'd guess #11242 is to blame---advance apologies. I can take a peek sometime in the next day or so. |
Good evidence that when the type-system rewrite gets underway, a good first step will be to look over our tests and see what's wrong/missing. |
Type{Tuple{}} should not be a subtype of Type{Tuple}. Fixes #17198
this should be an error, since a 3-element tuple can't be converted to a 1-element tuple, but instead it just ignored the trailing elements:
The text was updated successfully, but these errors were encountered: