hishamk

Analog, of course.

This looks real neat.

Thanks for the feedback. I've added a mermaidjs code generator for the ruleset.

Thanks for everyone's feedback. I've pushed out a few changes:

1- Regular slice instead of timestamp-keyed map. That didn't make sense in retrospect. 2- Better benchmarks. 3- Non-exported current state and transitions. Mutexed getters to avoid concurrency issues. 4- Variadic rule parameters. 5- Better example.

Thanks for the feedback.

The benchmark was for six transitions. I've now updated a few things and added new benchmarks.

I also got rid of timestamps for the map keys - it's back to a regular slice. In retrospect, that was a tad bit off, I agree.

Thank you so much for this head's up. I've just pushed out a new update that covers this and a few other changes.

Thank you. The focus was on simplicity and handling less complex scenarios. In my current projects the business logic lends itself to sitting outside the FSM/State Trooper. The logic dictates the transitions at arms length to the FSM. The FSM does not carry on any particular business logic, it just enforces the transition rules from one state to any number of possible states - hence why I've included the metadata aspect to embed info about the reason for a transition.

Re the visualization, I think that would be cool. I might give that a shot.

Ha! Not bad at all.

Thanks for this. You are indeed correct. I've pushed a fix and also added a race test to confirm the fix.

Thank you!

I’ve spent the better part of my pandemic commute-free time learning a long standing interest of mine, electronics. This is my first MCU board.