如何修复判断位掩码是否包含指定位的has_flag方法Bug？

Great catch on that bug! The issue is exactly what you noticed: since FLAG.DEFAULT is 0b0, any bitwise AND with 0b0 will always equal 0b0—so every value ends up appearing to include the DEFAULT flag, which breaks your mutual exclusivity rule.

Your current fix is totally valid, but there are a few other clean ways to address this depending on your needs:

1. Generic Zero-Check (No Hardcoded DEFAULT) #

Instead of explicitly checking against FLAG.DEFAULT, you can use the fact that 0 evaluates to False in Python. This makes the method more flexible if you ever change what DEFAULT is:

def has_flag(self, val):
    if not val:
        return self._descriptor == val
    return self._descriptor & val == val

2. Compact Conditional Expression #

If you prefer a one-liner, you can condense the logic into a ternary expression. This keeps things concise while still being readable:

def has_flag(self, val):
    return self._descriptor == val if not val else (self._descriptor & val == val)

3. Pattern Matching (Python 3.10+) #

If you're using a newer version of Python, pattern matching makes the intent super clear:

def has_flag(self, val):
    match val:
        case 0:
            return self._descriptor == 0
        case _:
            return self._descriptor & val == val

4. Adjust the DEFAULT Semantics (If Possible) #

If your use case allows it, you could redefine DEFAULT to use an unused bit instead of 0. This would make it behave like any other flag, eliminating the special case entirely:

class FLAG(IntEnum):
    DEFAULT = 0b1000  # Use an unused bit position
    FLAG_A = 0b0001
    FLAG_B = 0b0010

Note: This changes what DEFAULT means—it's now a distinct flag rather than "no flags set". Only use this if that aligns with your requirements.

All these approaches solve the core problem: ensuring that has_flag(FLAG.DEFAULT) only returns True when self._descriptor is actually 0, not for every value.

内容的提问来源于stack exchange，提问作者indigo153