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

Locked<T> or LockProtected<T> #10

Open
Xenoprimate opened this issue Feb 15, 2019 · 0 comments
Open

Locked<T> or LockProtected<T> #10

Xenoprimate opened this issue Feb 15, 2019 · 0 comments
Milestone

Comments

@Xenoprimate
Copy link
Contributor

I'd like a type that forces locking over a value (with a potentially user-supplied lock object). The purpose will be to help ensure synchronization can not be accidentally elided for the wrapped variable.

Including forcing locks for compound mutations, by way of a 'using' pattern usage. Or, could even only allow access to the variable if a nominated monitor object is entered at the time. Also I wonder if there's any way to protect against leaked references...

@Xenoprimate Xenoprimate added this to the 1.0 milestone Feb 15, 2019
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

No branches or pull requests

1 participant