Open mbver opened 2 weeks ago
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.
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.