README: all checks are now compatible with all major type checkers (#346

)

README.md

@@ -86,14 +86,6 @@ currently emitted:
 | Y051 | Y051 detects redundant unions between `Literal` types and builtin supertypes. For example, `Literal[5]` is redundant in the union `int \| Literal[5]`, and `Literal[True]` is redundant in the union `Literal[True] \| bool`.
 | Y052 | Y052 disallows assignments to constant values where the assignment does not have a type annotation. For example, `x = 0` in the global namespace is ambiguous in a stub, as there are four different types that could be inferred for the variable `x`: `int`, `Final[int]`, `Literal[0]`, or `Final[Literal[0]]`. Enum members are excluded from this check, as are various special assignments such as `__all__` and `__match_args__`.
 
-Many error codes enforce modern conventions, and some cannot yet be used in
-all cases:
-
-* Y037 (enforcing PEP 604 syntax everywhere) is not yet fully compatible with
-  the mypy type checker, which has
-  [a few bugs](https://github.com/python/mypy/issues?q=is%3Aopen+is%3Aissue+label%3Atopic-pep-604+label%3Atopic-type-alias)
-  regarding PEP 604 type aliases.
-
 Note that several error codes recommend using types from `typing_extensions` or
 `_typeshed`. Strictly speaking, these packages are not part of the standard
 library. However, these packages are included in typeshed's `stdlib/`