Vitaly Puzrin

Refactored LeapSink. Now sure about it :) - Correct and clear logic without compromises. Param fetch is guaranteed to be consistent via 2-phase commits. The concrete implementation can be improved...

Sure, inspected `etl::state_chart` prior to do anything (and the most popular FSM-s in another projects). It's a classic table-defined graph. "Must have", but for another kind of tasks. Autonomous FSM-s...

src: https://github.com/pdsink/pdsink/blob/master/src/pd/utils/afsm.h tests: https://github.com/pdsink/pdsink/tree/master/test/test_afsm Reworked namespace/naming for more friendly use. Added features: - Getting previous state ID. Sometimes convenient. I used external flags for workarounding when the feature was not...

Some updates after practice with the real project: - Fixed prev state tracking, if state changed from `.on_enter_state()`. - Enforced build error if entry/run/exit method declaration is missed. Behaviour may...

That looked a bit dangerous when doing this package. But you can invoke `extract` with `--orphaned-fail` to tests/CI. Will it help, or do you have frequent cases that require bulk...

If I remember right, there is a technical limitation—it is impossible to keep formatting and comments on a yaml override. So, all related features were skipped in favor of a...

It it a problem? What is the real use case to solve?

I understand it's technically possible to pass multiple thousands of params. Just interesting, where is this useful in the real world?

To be honest, v3 is very old, and i don't remember what happens there and is the used tooling still working. I have no principal objections about publishing v3 patch,...

Published. Please check and let me know how it is. @mhassan1 thank you very much