the problem I want to solve is that I have class r...
# announcements
o
the problem I want to solve is that I have class representing process, which does some work... and the class can have 0..n listeners/observers of the work... So... the listeners/observers can come and go at any time, and at he same time the process can "clean" the observers when it's done.. So I have shared list of observers, which can be "modified" from the client side and from the proces side itself... What would be right design of this structure, so I don't need to worry about multithreading... I am using coroutines for background tasks but that shouldn't be the concern here