Skip to content

Heap closures should always require a capture clause to capture mutable variables #2446

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.

Sign up for GitHub

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

Jump to bottom
Closed
msullivan opened this issue May 25, 2012 · 0 comments
Closed

Heap closures should always require a capture clause to capture mutable variables #2446

msullivan opened this issue May 25, 2012 · 0 comments
Labels
A-type-system Area: Type system

Comments

@msullivan
Copy link
Contributor

Right now, that doesn't happen if the use is considered to be a "last use". This is confusing and not particularly helpful.
@ghost ghost assigned msullivan May 25, 2012
@msullivan msullivan removed their assignment Jun 16, 2014
bors added a commit to rust-lang-ci/rust that referenced this issue Sep 22, 2022
@bors
Auto merge of rust-lang#2446 - RalfJung:rustup, r=RalfJung
c0cbddc 
add test for dyn call issue

Tests for rust-lang/miri#2432
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@zhassan-aws
Fix link in CHANGELOG.md (rust-lang#2446)
2df67e3
BoxyUwU pushed a commit to BoxyUwU/rust that referenced this issue Jun 3, 2025
@fmease
Merge pull request rust-lang#2446 from fmease/fix-warning-blocks
9649a9c 
Fix some warning blocks that contain Markdown
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-type-system Area: Type system
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msullivan