Add a lockable context for improved memory safety. #296
Conversation
This file contains 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
sebjameswml
requested changes
Dec 2, 2024
sebjameswml
approved these changes
Dec 2, 2024
|
I'm getting "Merge attempt failed" "Merge already in progress" which I think is some sort of Github UI bug. Otherwise, this would already have been merged. |
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.
there are now functions for contexts that mirror the mutex functionality that they represent. these are:
lockContexttryLockContextunlockContextThe underlying implementation just uses a
mutexto allow a thread to lock the context to its thread while performing GL commands.