-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Added pitfall hint about Lock::isAcquired() #11426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Ping @jderusse, I'm actually happy with the wording now, what do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great addition. Thank you @Toflar .
Just a small comment about the word| process
@Toflar could you please squash your commits into one? Unfortunately, because of different authors, we cannot do that for you 🙏 Thanks! |
Sure, rebased :) |
Thank you Yanick. |
This PR was merged into the 3.4 branch. Discussion ---------- Added pitfall hint about Lock::isAcquired() I've hit that issue on Friday so I figured I'd just add a hint so other devs don't make the same mistake 😄 /cc @jderusse (and thanks for the help!) Commits ------- 6660f2d Documented Lock::isAcquired() method
I've hit that issue on Friday so I figured I'd just add a hint so other devs don't make the same mistake 😄
/cc @jderusse (and thanks for the help!)