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

Procedure

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

I'd say P-low? It's a crash, but you have to do it intentionally and the fix is "don't do that"

i'd go with p-medium, even if it's p-medium generally you wouldn't want to crash

I guess my rationale is that I wouldn't want people to focus on this over other P-medium problems

it's not impacting anyone

Agree with the rationale, can we perhaps "fix" this somewhere else, like in the documentation? People are often experimenting and playing with things

A bit in the same spirit as this other issue

ohh hehe, I've just commented in #t-compiler/wg-prioritization/alerts > I-prioritize #76452 Low nproc ulimit causes compiler to cra… about exactly the P-low vs P-medium discussion there

agree with P-low here too

for instance, I understand @apiraino's and @DPC's thoughts that is a crash

the thing in my opinion is that Rust has too many crashes like those

if it were a rock solid that never crashes things like those could even be P-high but given that is not the case, I tend to lower the priority

that's fine for me. I just wonder if there is anything actionable for us to do in these cases, even if just forwarding the issue somewhere else

Issue #76424's prioritization request has been removed.

apiraino said:

that's fine for me. I just wonder if there is anything actionable for us to do in these cases, even if just forwarding the issue somewhere else

I don't think there's anything else for us to do but if it were we would rather focus on see what to do on P-high or P-critical instead I'd say :)