Don't suggest moving tuple structs with a significant drop to late evaluation

[Jarcho]

fixes #9608

changelog: Don't suggest moving tuple structs with a significant drop to late evaluation

[rust-highfive]

r? @Alexendoo

(rust-highfive has picked a reviewer for you, use r? to override)

[AlexTMjugador]

Thanks! I'm curious about how come this PR fixes the issue, given that the affected constructs do not have any intuitive "significant drop"? The Drop trait isn't implemented on them or any type they reference.

[Jarcho]

This is checking if the enum contains a significant drop, not just the variant being constructed. IIRC, any type which implements drop, but doesn't have the rustc_insignificant_dtor attribute is considered to be significant.

[Alexendoo]

👍

@bors r+

[bors]

📌 Commit 39a7d00 has been approved by Alexendoo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 39a7d00 with merge cf72565...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: Alexendoo
Pushing cf72565 to master...