Skip to content

Conversation

@mbver
Copy link

@mbver mbver commented Aug 26, 2024

as m.leave is atomic, there's no need to guard against concurrent access to m.Leave(). a check of m.hasLeft will reject the later calls to m.Leave once m.leave was set atomically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant