Does SyncExecutor assumed to have a concurrent access

[mrniko]

SyncExecutor seems to be implemented in a thread-safe manner. Right?

[Beh01der]

Correct.
Both sync and async executors are single-threaded and run tasks consequentially (next task starts only when current is completed). Thus, for logic, implemented within state / event handlers there is no concurrency.

[mrniko]

If it thread-safe why you need to use queue in SyncExecutor?

[Beh01der]

I wanted to isolate task execution.

Let's say we have handler for state State and in that handler we trigger event Event that moves FSM into state State2 that also has a handler.
If tasks are not separated, then execution flow will enter handler for State, then, when Event triggered execution flow will get into handler for State2, then it will return back to handler for State (if there is some code after trigger() call). To avoid it, I used queue.

With the queue, first, handler for State will be fully executed, and then, if event was triggered, handler for State2.

Also, SyncExecutor was ment mainly for unit tests, to avoid thread creation / waiting / termination but at the same time behave the same way as AsyncExecutor does.

[mrniko]

Ok, i was wrong.