Tracking issue: Rust Language features we want or are following
Open
Nobody has claimed this yet.
tracking
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
- https://github.com/rust-lang/rust/issues/130539 - Will make it possible to do
Atomic<f32>in the future. - https://github.com/rust-lang/rfcs/pull/3446 - Better allocator API
Contributor guide
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 reviewing the linked Rust issue 130539 and Rust RFC pull request 3446, then check how each relates to Rust-GPU. No repository file or test is named; done would mean determining the relevant status and keeping the tracking checklist current.
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