I have a

suspend

function that launches several operations (syncing individual pieces of local data) and I don't want this function to be run more than once simultaneously (if we try to POST the same data twice, then we get two new entries on the server side). What is the preferred practice for preventing a second simultaneous execution of this function? I have an idea, but I wanted the community opinion since there was some concern about my answer in a code review.

Shared

Mutex

instance +

withLock { }

usage.

That was what I went with. Although, I'm not sure what you mean by "shared"

Mutex

? Can/should I put it in the

companion object

so the function can only run once among all instances of the class (as opposed to preventing multiple calls to one instance)? Seems like that should still be safe as long as it remains a

private

value.

Yes, one private instance in a companion object is what I called "shared"

Thanks. For some reason I didn't think of that at first and I was considering trying to make the class a singleton to make sure there was only one mutex 🤦‍♂️.