Make state definition clearer

[hanekoo]

If local storage is not used, the state_machine macro could generate the following State enum, which would make the usage more straightforward and clear:

pub enum State { LedOn, NotBlinking { b }, LedOff }

impl State {
    fn led_on() -> Self { Self::LedOn } // no local storage
    fn not_blinking(b) -> Self { Self::NotBlinking { b } } // with local storage
    fn led_off() -> Self { Self::LedOff }
}

Call Handler :

match self {
    State::LedOn => Blinky::led_on(event), // no local storage
    State::NotBlinking { b } => Blinky::not_blinking(b, event), // Uses local storage
    State::LedOff => Blinky::led_off(event),
    _ => statig::Response::Super
}

Get State :

match state_machine.state() {
    State::LedOn => {} // no local storage or extra parameters
    State::NotBlinking { b } => {}
    State::LedOff => {}
}

This approach would enhance clarity and improve the developer experience by making state transitions and handling more intuitive.

[mdeloof]

Hi! Thank you for your comment, this would indeed make the generated code a bit cleaner. If you or somebedy else makes a PR with the necessary changes, I'll happily merge it :)