Feature request: implicit-flag-overlap #8102
Labels
Enhancement ✨
Improvement to a component
Needs PR
This issue is accepted, sufficiently specified and now needs an implementation
Milestone
Current problem
The following behaviour seemed confusing:
(note that this is an
IntFlag
, not anIntEnum
)Desired solution
The reason this happens is that
Flag
types are designed for setwise operations (bitwise operations, in the case ofIntFlag
), and, becauseC
can be composed ofA
andB
......internally,
IntFlag
considersC
to be an alias -- and doesn't include it when iterating over the members of the flag.A
pylint
message something along the lines ofimplicit-flag-overlap
could be emitted by a relevant checker when scanning the class declaration.Additional context
No response
The text was updated successfully, but these errors were encountered: