spawnStateless ignores onCrash property about nact HOT 2 CLOSED

Apologies for the tardy reply. Was just on holiday. You're correct in that the onCrash property is not respected in stateless actors. It was originally the case, and I missed updating documentation to reflect this.

The reasoning for changing the original behavior is because stateless actors process messages concurrently. Introducing a supervision policy to a concurrent process in practice results in a lot of undefined behavior. For example if you want the actor to stop after a single error, what happens to the other messages which are currently being processed by the actor? I felt that given that these actors have no state, introducing the extra complexity and mental overhead of a supervision policy would have little gain.

I've updated the documentation to use stateful actors instead of stateless ones in the supervision policy section.

from nact.

Makes sense, thank you.

from nact.