Is mutating "parent" state in a module an anti-pattern?

[LostKobrakai]

@codeanpeace

These might be signs that the LineReader would be better off as its own process i.e. Task/Agent/Genserver so it can keep track of its own state or rolled into ClientHandler. I’d be curious what else it’s being used for and how else it’s being used.

Imo processes should only be introduced if there are runtime level reasons for them - failure isolation, asynchronous processing, … That is completely separate from code level abstractions, where multiple module collaborate to build up logic.