struct_excessive_bools for different reasons?

Description

Using multiple bools like shown in the example seems like a complete beginner mistake to me.
I don't think I ever used multiple bools to mark progress. Even most beginners would just use a single number I guess.

(maybe this sometimes happens when some of the bools are supposed to be enabled at the same time, but not all of them)

I always get this error when creating settings.

For example the settings of a character in a game look like this:

struct PlayerSettings {
    can_jump: bool,
    can_run: bool,
    can_dash: bool,
    can_attack: bool,
    can_stomp: bool,
    ...
}

And in such a case, this implementation seems totally fine. That's probably why this lint is set to allow by default.

But I think using multiple bools in this case might still not be great. Because I got this lint, I turned such a struct into a bitset.

Something like this:

struct PlayerSettings {
    bits: u16
}

impl PlayerSettings {
    can_jump(&self) -> bool {
        self.bits & 1 > 0
    }

    can_run(&self) -> bool {
        self.bits & 2 > 0
    }

    can_dash(&self) -> bool {
        self.bits & 4 > 0
    }

    ...
}

So maybe instead of suggesting only state machines and enums, using bitsets could also be suggested here?

Version

rustc 1.92.0 (ded5c06cf 2025-12-08)
binary: rustc
commit-hash: ded5c06cf21d2b93bffd5d884aa6e96934ee4234
commit-date: 2025-12-08
host: x86_64-unknown-linux-gnu
release: 1.92.0
LLVM version: 21.1.3

Additional Labels

No response

Start by reviewing the struct_excessive_bools lint and the issue's discussion of state machines, enums, and bitsets. Determine the intended guidance and scope before identifying the relevant implementation and tests; the work is done when the agreed recommendation is documented in the lint behavior and covered by appropriate tests.