mirror of https://github.com/astral-sh/ruff
bf0bc87f06
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.) |
||
|---|---|---|
| .. | ||
| legacy | ||
| pep695 | ||
| builtins.md | ||
| scoping.md | ||
| specialize_constrained.md | ||