With literal types, the actual default value becomes relevant to type checkers in some cases (because in effect, two different values are different types).
I believe Y011 should be updated to accept a non-ellipsis default value that matches a Literal type in the annotation of that parameter.
With literal types, the actual default value becomes relevant to type checkers in some cases (because in effect, two different values are different types).
I believe Y011 should be updated to accept a non-ellipsis default value that matches a Literal type in the annotation of that parameter.