Isn't Enum better for WorkingKeys?

[omid]

It looks like WorkingKeys can be an Enum.
And so state.working_keys can be a simple array, or if you insist for the uniqueness, it can be a BTreeSet.

[pouriya]

We need to iterate on them in here so that's why we make them iterable here.
We also need to make some keys active/inactive (if any error occurs) here and that's why I preferred struct.
Do you have any suggestion?

[omid]

IMHO, WorkingKeys.to_info_list should actually return an array of a struct like this:

struct Key {
  shortcut: String,
  description: String,
  key: KeyEnum,
}

and then KeyEnum can be:

enum KeyEnum {
  Q,
  Up,
  Down,
...
}

I'm not so familiar with the source code.
But if you need to keep the enabled ones somewhere, maybe a Vec<&Key> can do the job.

PS: then it'll be better to impl PartialEq manually for Key.