Add `__match_args__` to `Event` for `type`

[aatle]

match statements are good for pygame events.

match event:
    case Event(type=pygame.MOUSEBUTTONDOWN, pos=(x, y)):
        print(x, y)

(Maybe that should be documented.)

If __match_args__ = ("type,") was added to Event, then type would be positional so that type= doesn't need to be written:

match event:
    case Event(pygame.MOUSEBUTTONDOWN, pos=(x, y)):
        print(x, y)

__match_args__ could also be added to classes like Rect and Vector2/3 but I don't think there are many use cases.

https://docs.python.org/3/tutorial/controlflow.html#match-statements

[Starbuck5]

Dang, that's kinda cool. I didn't know that either of those things were possible with Event.

I think this could conflict with my pygame-ce 3.0 proposal: #2759

If mousebuttondown was a class, it could just be case pygame.MouseButtonDown.

[aatle]

It would not conflict with your proposal.
The __match_args__ arguments are still optional so case MouseButtonDown() would work at the same time as case Event(pygame.MOUSEBUTTONDOWN). This means adding __match_args__ is just a syntactical improvement that makes match better, in the meantime before your proposal is implemented.

match statements actually complement your proposal perfectly IMO, they both benefit each other.