Stream: t-compiler/wg-prioritization/alerts

Topic: I-prioritize #78140 regression: array methods unstable feat…

triagebot (Oct 20 2020 at 13:49, on Zulip):

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


Stu (Oct 20 2020 at 14:31, on Zulip):

Shouldn’t this be critical since it breaks stability guarantees?

Mason Stallmo (Oct 20 2020 at 15:50, on Zulip):

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 !

DPC (Oct 20 2020 at 16:45, on Zulip):

it's an unstable feature though

Camelid (Oct 20 2020 at 19:05, on Zulip):

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.

Camelid (Oct 20 2020 at 19:09, on Zulip):

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.

Camelid (Oct 20 2020 at 19:09, on Zulip):

I think this should be P-high

triagebot (Oct 21 2020 at 20:43, on Zulip):

Issue #78140's prioritization request has been removed.

Last update: Apr 10 2021 at 21:45UTC