ruff/crates/ty_python_semantic/resources
Luca Chiodini bf0bc87f06
Uniformly use "not supported" in diagnostics
Some (most?) diagnostic messages already use the form
"Operator <op> not supported", but others use "Operator <op> unsupported":

https://play.ty.dev/ae13cd3d-531b-4ed3-adea-eba9b0cafb6c
```py
0 + ""
0 < ""
```
> Operator `+` is unsupported between objects of type `Literal[0]` and `Literal[""]` (unsupported-operator) [Ln 1, Col 1]
> Operator `<` is not supported between objects of type `Literal[0]` and `Literal[""]` (unsupported-operator) [Ln 2, Col 1]

This commit uniforms the diagnostic messages, favoring "not supported".
While it is two characters longer, this matches pyright/pyrefly's
messages, is slightly less redundant given that
"unsupported" already appears in the diagnostic's type
(e.g., unsupported-operator), and makes the "not" stand out.

(This commit does not remove all occurrences of "unsupported" in diagnostic messages:
there are still some that e.g. start with "Unsupported <X>".
I think those are acceptable as they are.)
2025-12-11 14:47:50 +01:00
..
corpus [ty] Add test case for fixed panic (#21832) 2025-12-07 15:58:11 +00:00
mdtest Uniformly use "not supported" in diagnostics 2025-12-11 14:47:50 +01:00
primer [ty] Add missing projects to `good.txt` (#21721) 2025-12-01 11:18:41 +01:00
README.md Rename Red Knot (#17820) 2025-05-03 19:49:15 +02:00

README.md

Markdown files within the mdtest/ subdirectory are tests of type inference and type checking; executed by the tests/mdtest.rs integration test.

See crates/ty_test/README.md for documentation of this test format.