David Peter 5b6e94981d [red-knot] Silence unresolved-attribute in unreachable code (#17305) ...

## Summary

Basically just repeat the same thing that we did for
`unresolved-reference`, but now for attribute expressions.

We now also handle the case where the unresolved attribute (or the
unresolved reference) diagnostic originates from a stringified type
annotation.

And I made the evaluation of reachability constraints lazy (will only be
evaluated right before we are about to emit a diagnostic).

## Test Plan

New Markdown tests for stringified annotations.

2025-04-10 17:15:47 +02:00

..

resources

[red-knot] Silence unresolved-attribute in unreachable code (#17305)

2025-04-10 17:15:47 +02:00

src

[red-knot] Silence unresolved-attribute in unreachable code (#17305)

2025-04-10 17:15:47 +02:00

tests

[red-knot] Add GitHub PR annotations when mdtests fail in CI (#17150)

2025-04-02 21:51:52 +01:00

build.rs

Modernize build scripts (#13837)

2024-10-20 22:35:35 +01:00

Cargo.toml

[red-knot] Add a test to ensure that KnownClass::try_from_file_and_name() is kept up to date (#16326)

2025-02-24 12:14:20 +00:00

mdtest.py

mdtest.py: do a full mdtest run immediately when the script is executed (#17128)

2025-04-01 19:27:55 +01:00

mdtest.py.lock

[red-knot] Markdown test runner (#15632)

2025-01-21 14:06:35 +01:00