-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Wrong error message for move_ref_pattern #69348
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
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Thanks. You need to |
Could you squash the commits into one? r=me rollup with that done. |
Bless tests
0005e17
to
38a22b8
Compare
@Centril Done |
@bors r+ rollup |
📌 Commit 38a22b8 has been approved by |
Rollup of 7 pull requests Successful merges: - #68984 (Make `u8::is_ascii` a stable `const fn`) - #69339 (Add test for #69312) - #69346 (Clean up E0323, E0324, E0325 and E0326 explanations) - #69348 (Wrong error message for move_ref_pattern) - #69349 (MIR is not an experiment anymore) - #69354 (Test `Duration::new` panics on overflow) - #69370 (move const_eval.rs into the module folder) Failed merges: r? @ghost
The current error message states that move occurs because of
Copy
:"move occurs because `{}` has type `{}` which does implement the `Copy` trait."
I found this randomly when surfing through the sources. This means, I don't have any context and might be completely wrong.
r? @Centril