@WG-prioritization/alerts issue #79904 has been requested for prioritization.
I-nominated
?@WG-prioritization this needs a comment
what about this one?
I guess we should or either group as fallout of Matthew Jasper traits PR if that's the case
but maybe just even go with P-critical
?
maybe it's a different flavor of the same kind of issue
but I guess if we have it open and with I-prioritize
I'd go with P-critical
this was marked as wontfix in the linked issue: https://github.com/rust-lang/rust/issues/77638#issuecomment-708074295
so I don't think it makes sense to have an independent issue and prioritize that
we should double check it is the same issue though
ok
@Joshua Nelson can you add a comment to the issue stating this?
given that you have more context
done
Santiago Pastorino said:
given that you have more context
well, not me personally :laughing: I just read the linked issue
yeah right :)
I added a comment to this issue stating that I don't believe we should close this (and that even closing #77638 seems suspect). Given this impacted several crates in the last crater run, I think the compiler team should at least discuss this.
I-nominate definitely makes sense to me
Can I add I-nominate using @rustbot label
?
You may not have permissions - can you try? If it doesn't work I'll add it, but having the record is nice when T-compiler pings people in the meeting haha
Doesn't look like I do. Nothing happened :-)
@apiraino thanks for the help!
tried, failed and manually applied the label :laughing:
but that issue I think it belongs to a larger story with some other issues opened in the last days, they're all relevant to crater
runs failing
Those other issues all seemed to be closed. The reason I decided to say something is I was worried the entire issue would be lost
I'll try to quickly add something to the agenda about this issue (the meeting starts in ~1h)
the "Nominated Issues" section looks already pretty packed, not sure the team can manage to look at everything (might slip to the next time)
(note to self) issue didnt make it to the meeting, but it's on the radar
This is probably related to #78893 which was mentioned and noted as P-critical
Issue #79904's prioritization request has been removed.
simulacrum removed I-prioritize
simulacrum: Okay, sounds like won't fix and that we should note the fix for #27675 as a compatibility note. Assigning to @XAMPPRocky to do so (and close this issue once you have done so).