Actor.processSystemMsg

All system messages are handled.

Assuming: * they are not heavy to process * very important that if there are any they should be handled as soon as possible * ignoring the case when there is a "storm" of system messages which "could" overload the actor system and lead to a crash. I classify this, for now, as intentional, malicious coding by the developer themself. External inputs that could trigger such a behavior should be controlled and limited. Other types of input such as a developer trying to break the actor system is out of scope.

struct Actor
package package @safe
void
processSystemMsg
()

Meta