-
Notifications
You must be signed in to change notification settings - Fork 13k
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
A tutorial to demonstrate practical alternatives to unsafe shared mutable state #8395
Comments
Triage: no such tutorial (or "Guide") yet. |
part of #11755 |
We talk about this concept in a nubmer of other places, and I'm not sure that it deserves a full tutorial on its own. |
Yes, this is basically subsumed by 'write a better threads guide', which is already an open bug. comparing and contrasting different ways of dealing with shared state belongs there. |
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this issue
Feb 5, 2015
Fixes rust-lang#18936 Fixes rust-lang#18938 Fixes rust-lang#20038 Fixes rust-lang#8395 Fixes rust-lang#2080 Fixes rust-lang#21194
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rust deliberately restricts the use of shared mutable state out of concern for safety. However, this is no solace to users coming from other languages who are used to making effective use of shared mutable state to Get Things Done. We need a document that describes practical approaches used in rustc and Servo to safely work around this restriction.
The text was updated successfully, but these errors were encountered: