Skip to content
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

Separate locking from static range #540

Merged
merged 1 commit into from
Sep 8, 2022
Merged

Conversation

mjp41
Copy link
Member

@mjp41 mjp41 commented Jun 7, 2022

Pull a part the locking from the static range. This enables
locking to be added to a range directly, and does not require
it to be made static. This is useful in cases where the source
of memory is shared between threads, but not static. I.e. there
are multiple instances of the same type.

@mjp41 mjp41 requested a review from davidchisnall June 7, 2022 14:44
@mjp41
Copy link
Member Author

mjp41 commented Jun 7, 2022

This isn't actually required by the process_sandbox usage. I think it is still nice to pull apart, so I have left the PR up. But it can be dropped.

Pull a part the locking from the static range. This enables
locking to be added to a range directly, and does not require
it to be made static.  This is useful in cases where the source
of memory is shared between threads, but not static.  I.e. there
are multiple instances of the same type.
@mjp41 mjp41 merged commit a118c9b into microsoft:main Sep 8, 2022
@mjp41 mjp41 deleted the lock_range branch September 8, 2022 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants