@WG-prioritization/alerts issue #78140 has been requested for prioritization.
Shouldn’t this be critical since it breaks stability guarantees?
I'm on the fence here about if we should add a priority to this at all. It seems like the lang team discussed this already and settled on the fact that it's a bug fix and to let it ride I'm not sure that the handful of crater failures would move the needle very far from the decision reached previously. I could be miss-reading this though.
Sorry wrong thread !
it's an unstable feature though
I feel a bit confused by the description -- it seems like it might be affecting stable code due to some kind of inference? Also, I don't think simulacrum would have tagged with regression if it were unstable code. I'll ask in the issue.
I just read it over again: this appears to be affecting beta-channel code, not nightly code. It seems like it's caused by type inference changing because of
as_slice* being added.
I think this should be
Issue #78140's prioritization request has been removed.