Stream: t-compiler/wg-prioritization/alerts

Topic: #81757 1500-arm match statement causing a major build time …

triagebot (Feb 06 2021 at 04:19, on Zulip):

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


Camelid (Feb 06 2021 at 04:19, on Zulip):

Should we ping the LLVM group here?

Joshua Nelson (Feb 06 2021 at 04:21, on Zulip):

I don't think this is easily actionable, I think we should only ping when there's something actionable

Camelid (Feb 06 2021 at 04:21, on Zulip):

The action would be "investigate the issue" ;)

apiraino (Feb 11 2021 at 11:07, on Zulip):

@Camelid meanwhile Nikita Popov commented on the issue so I think now the LLVM group has this under their radar. I'd leave them a bit more time and see how this should be prioritized (unclear to me for now).

apiraino (Feb 25 2021 at 12:27, on Zulip):

I will remove the I-prioritize here because I'm not sure yet if there's an actionable. I /think/ it's not high/critical because it can be avoided by moving things in the code.

Nothing blocking prioritizing it again as the situation gets clearer

triagebot (Feb 25 2021 at 12:29, on Zulip):

Issue #81757's prioritization request has been removed.

Last update: Apr 16 2021 at 23:30UTC