@WG-prioritization/alerts issue #80303 has been requested for prioritization.
I would assign a
p-critical. At least a
p-high. The reason I can think of is preventing to reach stable and cause (what I think could be) important regressions. This issue looks to already have a hero assigned Stu
@apiraino IIUC, this isn't a regression.
Seems like P-medium or P-high to me. Maybe P-high.
hm ... interesting, then I probably misunderstood the context. I thought that the core of the problem was that vecdeque does not give the same result as another hashing package
hasher (like, vecdeque doesn't find an element when it should).
I'm not exactly sure what the underlying issue is, but I don't think it's a regression. Or, if it is, it's already hit stable.
this issue is being taken care of, I see a PR in the pipeline.
I think I will assign a
P-medium for now like Camelid suggested.
A P-high means that it would get briefly under the compiler team scrutiny tomorrow. If there's an advantage in that, then maybe better a P-high.
Issue #80303's prioritization request has been removed.