Stream: t-compiler/wg-prioritization/alerts

Topic: #80706 ICE(stable): thread 'rustc' panicked at 'called `Opt…

triagebot (Jan 05 2021 at 17:20, on Zulip):

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


Camelid (Jan 06 2021 at 01:38, on Zulip):

Seems like maybe P-high? Regressed in 1.48. Working code -> ICE

apiraino (Jan 06 2021 at 10:44, on Zulip):

If that code is supposed to compile, then yes definitively. I'd love to see more prominently mentioned somewhere if the expected behaviour is the have code compiling (there is a slight mention at the beginning of this comment), that would raising red flags at a glance.

apiraino (Jan 06 2021 at 10:45, on Zulip):

we prioritize a lot of ICEs as p-mediums with broken code showing weird errors

apiraino (Jan 06 2021 at 10:47, on Zulip):

(in this case, a p-high is probably more correct)

Ryan Levick (Jan 06 2021 at 10:50, on Zulip):

It would be nice if the example were even more minimal. It's hard to see how many different parts need to come together to trigger the issue making it hard to prioritize

apiraino (Jan 06 2021 at 10:57, on Zulip):

the "moving parts" of a reproducible example are the fun of trying to minimize a sample. Touching bits here and there can trigger different behaviour (as comments show). my understanding is that doesnt look easy to shrink down to few lines.
It would really interesting to have mini-workshops or live streams while hunting for mcve on issues :)

triagebot (Jan 07 2021 at 10:49, on Zulip):

Issue #80706's prioritization request has been removed.

Last update: Apr 15 2021 at 01:00UTC