-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Use Never
instead of None
for stores
#13984
Conversation
@@ -93,7 +92,7 @@ reveal_type(d) # revealed: Unknown | |||
### Starred expression (2) | |||
|
|||
```py | |||
[a, *b, c] = (1, 2) # error: "Object of type `None` is not iterable" | |||
[a, *b, c] = (1, 2) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm having trouble tracing this -- where is this diagnostic even coming from today?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the issue? Is this failing? I think that's probably coming from infer_starred_expression
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The diagnostic is no longer showing up, so I had to remove these assertions along with the TODOs to remove them (?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think that's correct. The diagnostics shouldn't be present in these cases and I think I left out one TODO in this specific case which might've confused you (?). The reason these diagnostics were showing up in the first place is because red knot tries to infer the starred expression (*b
) but that isn't supported yet, before this PR it would've returned None
and then it would raise a "not-an-iterable" diagnostic. But, it's now changed to use Never
in this PR.
ruff/crates/red_knot_python_semantic/src/types/infer.rs
Lines 2341 to 2344 in c6b8215
let iterable_ty = self.infer_expression(value); | |
iterable_ty | |
.iterate(self.db) | |
.unwrap_with_diagnostic(value.as_ref().into(), self); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR shouldn't even affect this case (we should never use the type of a Store-context expression), but it does just because we don't support assigning to Starred yet, and the way the temporary code works out, it does currently try to iterate the inferred type of a Store-context expression. But not throwing the error is better, so if anything switching from None
to Never
is an improvement here.
|
@@ -93,7 +92,7 @@ reveal_type(d) # revealed: Unknown | |||
### Starred expression (2) | |||
|
|||
```py | |||
[a, *b, c] = (1, 2) # error: "Object of type `None` is not iterable" | |||
[a, *b, c] = (1, 2) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR shouldn't even affect this case (we should never use the type of a Store-context expression), but it does just because we don't support assigning to Starred yet, and the way the temporary code works out, it does currently try to iterate the inferred type of a Store-context expression. But not throwing the error is better, so if anything switching from None
to Never
is an improvement here.
Summary
See: #13981 (comment)