Improve handling of mainThreadPrefix
and remove redundant null check
#34746
+2
−2
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.
This Pull Request refactors the
isCurrentThreadAllowedToHoldSingletonLock
method to improve the consistency ofmainThreadPrefix
variable usage and remove a redundant null check.Changes
Consistent Variable Usage
this.mainThreadPrefix
to the local variablemainThreadPrefix
at the beginning of the method, the subsequentif
check now consistently uses the local variable (if (mainThreadPrefix != null)
instead of if(this.mainThreadPrefix != null)
).Removed Redundant Null Check
mainThreadPrefix != null
check within theelse if (this.strictLocking == null)
block has been removed.if (maainThreadPrefix != null)
condition has already passed, guaranteeing the variable is not null at that point.I hope my PR useful :)
Thank you.