You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mishamsk
changed the title
[red-knot] Check __init__ arguments on class literals call
[red-knot] Check __init__ arguments when doing try_call on a class literal
Mar 5, 2025
mishamsk
changed the title
[red-knot] Check __init__ arguments when doing try_call on a class literal
[red-knot] Check __init__ arguments when doing try_call on a class literal
Mar 5, 2025
Description
Currently red knot assumes all calls to class literals are valid and create instances. E.g. this test yields no diagnostic currently
We should check
__init__
signature just like any other call and emit diagnostics.This is step 1 in a series of feature to support the instance creation process in full. The related logic of handling
type[C]
is tracked in #15948The text was updated successfully, but these errors were encountered: