@WG-prioritization/alerts issue #80365 has been requested for prioritization.
I don't think this is actually UB, but Miri thinks it is, so figured it was worth prioritizing.
(aka, making sure other people take a look at it)
Actually, based on what people said on the issue, it seems Miri is correct in thinking it's UB: somewhere internally in
Weak::as_ptr (which is called by
Weak::into_raw), it's creating a reference out of an invalid raw pointer.
So this is unsound.
hum ... we didnt assign a priority label but now there is already a PR for this issue. I would simply remove remove the
I-prioritize label. @DPC would it make sense to assign a priority now?
I mean: is it useful if it goes into this weeks' agenda?
I think it's still useful to assign a priority; if the PR gets stuck it will help push it along and stop it from being lost.
Seems like P-high to me.
Ah, didn't realize the PR was merged.
But still nice to assign a "post-mortem" priority as you say :)