Remove unnecessary lock of changeState #631
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
There's no need to lock the
changeState
method. We don't need the whole operation is atomic. Instead, we just need thatc.setState(state)
takes effect so thatc.cond.Broadcast()
can broadcast the correct notification that the state has been changed successfully. #451 changedstate
field to an atomic variable, so we don't need the lock for changingstate
anymore.I guess the lock for
changeState
was added when thestate
field was just a normalint32
variable. But #451 didn't remove the lock.Modifications
Remove the
Lock()
/Unlock()
calls inchangeState
, then reusechangeState
inconnection.Close()
.Verifying this change
This change is a trivial rework / code cleanup without any test coverage.