@WG-prioritization/alerts issue #76432 has been requested for prioritization.
Hi, was looking into this, trying to get my head around the way this works. Due to it being an unsoundness bug we are in P-High/P-Crit territory?
that sounds right
although this one is a little odd because miri caught it, so it might not be affecting code in the wild
I would say P-high maybe?
Yeah, ngl first experience with Miri today haha, and yeah, isn't a crit in my eyes
P-high makes sense I think. We recently changed
mir-opt-level=3 to mean that these opts have a compile time cost but are not unsound
before that there were quite a few known unsound opts at
@lcnr do you happen to know the default for the compiler that's released?
mir-opt-level can only be set on nightly, so this is definitely not
mir-opt-level=1 I think
See https://github.com/rust-lang/compiler-team/issues/319 for the current design (at least I think that this is the current one :laughing: )
Yeah, I'm working on implementing part of that MCP.
IMO this is P-medium since you have to use
-Zmir-opt-level=3 and you can only do so on nightly. There's no way a stable or beta user could be affected.
-Zmir-opt-level=3 has had unsoundness for a long time anyway so this not a recent issue by any means.
ah, I thought that the MCP was already implemented. In this case
P-medium also seems fine to me.
agreed with p-med
It looks like no one applied the
P-medium label. I tried to apply it but I guess it won't work until the team PR gets merged :)
Issue #76432's prioritization request has been removed.