Repository navigation
docs: complete the OS_LOCKING_OK flag documentation - #372
Merged
Merged
Conversation
Fixes parallaxsecond#371 Signed-off-by: Srinivas Chippagiri <cvas22@gmail.com>
hug-dev
approved these changes
Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #371
The doc comment on
CInitializeFlags::OS_LOCKING_OKstopped mid-sentence. It now says that the library may use the native operating system locking primitives to make itself thread-safe, instead of custom mutex functions. Documentation only, no code changes.