On 2/25/21 7:07 AM, Markus Armbruster wrote:
Unfortunately, the "check" in check_exprs falls off almost immediately.
What do you mean by "falls off"?
mypy loses the constraint in its static analysis. i.e. all of the work
we do in expr.py is almost entirely opaque to mypy.
John Snow writes:
> On 2/24/21 7:32 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> Casts are instructions to the type checker only, they aren't "safe" and
>>> should probably be avoided in general. In this case, when we perform
>>> type checking on a nested structure, the type of each
On 2/24/21 7:32 AM, Markus Armbruster wrote:
John Snow writes:
Casts are instructions to the type checker only, they aren't "safe" and
should probably be avoided in general. In this case, when we perform
type checking on a nested structure, the type of each field does not
"stick".
We don't ne
John Snow writes:
> Casts are instructions to the type checker only, they aren't "safe" and
> should probably be avoided in general. In this case, when we perform
> type checking on a nested structure, the type of each field does not
> "stick".
>
> We don't need to assert that something is a str
Casts are instructions to the type checker only, they aren't "safe" and
should probably be avoided in general. In this case, when we perform
type checking on a nested structure, the type of each field does not
"stick".
We don't need to assert that something is a str if we've already checked
that i
