-
Notifications
You must be signed in to change notification settings - Fork 13.4k
2229: Don't move out of drop type #88477
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
a677558
to
3d7c237
Compare
3d7c237
to
33c6b94
Compare
33c6b94
to
153aa71
Compare
@rfcbot fcp merge As discussed in our [last triage meeting], this is an interesting semantic question and a tweak to the closure rules. I've written up the my conclusion in this hackmd, which also includes a number of other details. I wanted to do an FCP to get ✅ from the @rust-lang/lang team that they've seen this change. There is some urgency here owing to the Rust 2021 edition timeline. |
Team member @nikomatsakis has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
@@ -626,7 +633,7 @@ impl<'a, 'tcx> FnCtxt<'a, 'tcx> { | |||
self.tcx.struct_span_lint_hir( | |||
lint::builtin::RUST_2021_INCOMPATIBLE_CLOSURE_CAPTURES, | |||
closure_hir_id, | |||
closure_head_span, | |||
closure_head_span, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am a bit surprised that rustfmt isn't complaining about this extra space.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm surprised ./x.py fmt
made this change 😂
@arora-aman Not a big deal at all, but was it intentional that you renamed this PR from |
wwops, the commit didn't need to be there. But yes we changed how we handle the issue -- so I updated the title |
(Also just noting that I think this will need to be backported to beta now that the branch has happened.) |
I was convinced in the triage meeting that there are already enough consequences of @rfcbot reviewed |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
@bors r+ p=1 Rust 2021 related |
📌 Commit 153aa71 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (0d0d2fe): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
I moved the document to this design doc on the rfc-2229 repo: https://github.com/rust-lang/project-rfc-2229/blob/master/design-doc-closure-capture-drop-copy-structs.md |
…ulacrum [beta] bootstrap bump and backports This bumps the beta bootstrap compiler to the released 1.55.0, and backports the following PRs: * Drop 1.56 stabilizations from 1.55 release notes rust-lang#88694 * 2229: Don't move out of drop type rust-lang#88477 * Work around CI issue with windows sdk 10.0.20348.0. rust-lang#88797 Cargo update: 1 commits in 18751dd3f238d94d384a7fe967abfac06cbfe0b9..d199d817e4bb70facc710716e73b5dddf80bc055 2021-09-01 14:26:00 +0000 to 2021-09-09 14:08:56 +0000 - [beta] Fix `cargo fix --edition` on stable. (rust-lang/cargo#9891) r? `@Mark-Simulacrum`
Fixes #88476
r? @nikomatsakis