rust-lang / rust-lang/libs-team
Poisoning survey analysis
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 178
- Forks
- 28
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
Did any analysis or action come out of the poisioning survey? I see that the the survey results are in this repo but I can't see or remember anything coming out of that. I'm raising this because lock poisoning (and duration_since race conditions) has made my team fearful of concurrency in Rust, which has made me sad, but I can't see an obvious solution.
This came up in RustConf so I'll cc @nikomatsakis (I can't find the others on GitHub 😢)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the poisoning survey results in the repository and read them alongside any existing notes or follow-up references. Check specifically whether lock poisoning and duration_since race conditions received analysis or action; done means recording the conclusions and any clearly identified follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100