sobolevn
sobolevn
yes, I think so!
I've changed your issue to be a completely different one, because github is broken and I cannot post new issues for some reason.
Ok, seems reasonable. Please, send a PR
Yes, we should ignore this case. 1. We can ignore all cases in annotations 2. What to do with type aliases on module and class levels?
One way to allow `*TVT` is to allow it in `SomeType[*TVT]`, but not in `[*TVT]` I will comment on `Literal` later, I am focusing on one task per commit right...
@dependabot rebase
Yes, this is actually a good exception for this rule. python3.11 has `StrEnum` to help.
Hm, interesting. The other way would be: ```python >>> match (None, 2): ... case (x, _) if x is not None: ... raise ValueError ... ``` But, I agree that...
`pass` here means exactly what it should do in the first place: nothing. So, providing `pass` in a `case` statement means that this case does not do anything. As far...
This would be a breaking change. Moreover, we use some deps in our source code. However, I am 100% open to `wemake-python-styleguide[plain]` if that is going to work.