@WG-prioritization/alerts issue #79708 has been requested for prioritization.
(deleted - wrong thread)
No idea what priority this should be :laughing:
I think P-high or P-critical since this is unsound
I only suggest P-high because it's been around from 2015, but it's impacting people in production so P-critical seems appropriate
Higher priority is safer than lower :)
I think let's wait for some more people to jump in perhaps before we prioritize
Or you can label with P-critical if you think that's right
i guess p-high would be fine on this one
If it's that old, it probably occurs rarely.
P-high is fine, I think.
Hmm, I agree with Joshua that this should be P-critical since it's unsound and impacting people in production.
I don't have a strong opinion, I'm fine with
I'm not used to looking at LLCM bugs... From what I undestand from https://reviews.llvm.org/D91576, this is now fixed on LLVM upstream?
most likely 1.47.0 just exposed inputs that trigger it
So this may not actually be an issue that's been here since 2015 in Rust?
P-critical sounds right, and maybe
I-nominated to discuss a cherry-pick of the LLVM patch?
i guess we don't need both then, i-nominated should suffice imo
Issue #79708's prioritization request has been removed.
I'll fill the agenda for the issue now I guess