Rust needs a memory model
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
As noted by @arielb1, we need an organized place for resolving questions about the Rust memory model.
While I could have made this a post on internals.rust-lang.org, I think this topic 1. needs visibility, and 2. needs to be able to be easily cross-referenced by the other issues and discussions that are hosted on github.
Eventually such discussion will hopefully culminate in an actual RFC document with a definition of the Rust memory model.
So, this issue is meant to be a collecting place for either such discussion, (or linking other discussions that perhaps should funnel into here).
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
Start by reading the discussion in this issue and the linked Rust issue #30500, including the referenced comment, to understand the unresolved memory-model questions. Done would be an RFC that defines the Rust memory model; this issue names no implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100