@WG-prioritization/alerts issue #27675 has been requested for prioritization.

Procedure

• Priority?
• Regression?
• Notify people/groups?
• Needs I-nominated?

Being able make any type Copy seems very scary indeed

I'm not as familiar with this issue as other but looking through the conversation it seems like this would be a good candidate for P-Critical.

Yeah that seems like a very scary/bad thing indeed

Was that bug unnoticed since 2015?

If so I’m not sure it should be P-critical

I just noticed that it's at least been around since 2016.

Do the new comments on the issue warrant upgrading from a P-medium since that's what it was labeled as previously?

See also https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Soundness.20issue.20that.20makes.20any.20type.20Copy

I think P-high would be fine here

Seems good to me :+1:

If this bug stayed this long unnoticed, I guess it means that it's hard to encounter it in real code

@lcnr any additional thoughts?

The bug is already old and you can't easily trigger it by accident, so P-high seems fine

that's one of these bugs which makes rust look bad though, so I really want to see this fixed

(similar to https://blog.rust-lang.org/2020/07/30/Rust-1.45.1.html)

Tagging as P-highunless there are any objections

Issue #27675's prioritization request has been removed.