@WG-prioritization/alerts issue #46345 has been requested for prioritization.
there are two separate issues here and I'm not sure which @Camelid wanted us to prioritize
the first is 'sometimes my computer runs out of available threads' which we can't do anything about
the second is 'the error code is interpreted as EWOULDBLOCK instead of EAGAIN
the second IMO is P-low, the only thing it affects is Debug output (not even Display)
I thought the issue was that spawning the thread might take a few seconds, but rustc panics immediately
Is that not correct?
no, that's user code panicking, not hte compiler
they need to handle the error somehow, the standard library can't do it for them
Sorry, what I mean is this code seems to be used by the compiler, which can cause panics: #72482
that's a separate issue
I don't think it should have been marked as a duplicate
Oh. Reopen it if you see fit!
I may have been a bit over-eager when triaging :smile:
and my vote for the current issue (46345) is P-low
left a comment on the issue
thanks @Camelid and @Joshua Nelson for the analysis. Going for
P-low as suggested :thumbs_up:
I wonder why triagebot didn't pick up the state change...
when the issue is renamed after it has been labeled for prioritisation, the notification arrives in the new thread :laughter_tears: