rust-lang / rust-lang/rfcs

More control over closure `move`

Open
#1,377 3 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-lang
Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

Currently move takes ownership over all the variables in the environment of the closure. It would be nice to have finer grained control and be able to only move certain variables, perhaps with syntax like

move {x, y} |a, b| { ... }

See also https://github.com/rust-lang/rust/issues/29996

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read issue #1377 and the related rust-lang/rust issue #29996 first. The work requires determining the intended semantics and syntax for selecting which closure-captured variables are moved, then documenting an agreed design in an RFC; done means the proposal has a settled scope and reviewable specification.

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
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.