PEP 702's @deprecated, @overload, and __new__()

[finite-state-machine]

Describe the bug
Changes associated with #4456 add support for much of PEP 702, but the implementation currently fails to warn about use of a @deprecated @overload of __new__().

This is being filed as a separate issue (rather than a comment on #4456) at @erictraut's request.

Code or Screenshots

pyright-play.net

from __future__ import annotations

# pyright: strict

from typing import (
        Union,
        overload,
        )

from typing_extensions import (
        Self,
        deprecated,
        )


class ClassWithInit:

    @overload
    def __init__(self, value: int, /) -> None: ...
    @deprecated("passing strings is deprecated")
    @overload
    def __init__(self, value: str, /) -> None: ...

    def __init__(self, value: Union[int, str], /) -> None:
        pass

class ClassWithNew:

    @overload
    def __new__(cls, value: int, /) -> Self: ...
    @deprecated("passing strings is deprecated")
    @overload
    def __new__(cls, value: str, /) -> Self: ...

    def __new__(cls, value: Union[int, str], /) -> Self:
        return super().__new__(cls)


ClassWithInit(42)           # no error, as expected
ClassWithInit('forty-two')  # "The constructor for class 'ClassWithInit' is deprecated" as expected
ClassWithNew(42)            # no error, as expected
ClassWithNew('forty-two')   # got: no error; expected: similar error to above

VS Code extension or command-line
Pyright command-line 1.1.373

[erictraut]

This is addressed in pyright 1.1.374.