A modern programming language that makes developers happier.

kotlinlang

Apart of that, I’m working on an issue where we have a long running action (long networking ...) and we restart the same action. Then we enqueue things, and we wait for all the actions to complete. I’m thinking to propose a way of cancelling the running action, to help restart it

To do that I'd start a job for the long running operation, but if I need, I can cancel it. And, optionally, dispatch the same action again

then you keep a local reference for the job then

Well, you either have a reference to that job or to the action

To be able to restart the specific action

how do you restart a specific action then? :thinking_face:

That's what you proposed: the ability to restart an action. So, if that were possible, you'd either keep reference to the job or to the action you'd want to restart

What I mean to say is: I'm unaware of a use case for restarting an action, while we could encapsulate that behaviour in the view model by keeping reference to the job and cancelling it when needed. But there might be other use cases.