@WG-prioritization/alerts issue #67497 has been requested for prioritization.
P-critical, probably. Working code + unsoundness = bad.
tier 1 platform,
P-critical seems fine
Issue #67497's prioritization request has been removed.
P-critical, feel free to assign a different prio or discuss (either here or on the issue) if you feel otherwise.
I had a closer look at this issue and the linked comments: I am not completely sure it affects a tier 1 platform, my understanding is that it affects the windows 32 bit "world" so to say. The problem seems to stem from installing 32 bit node js stuff over Windows 64bit , see linked issue #1 and #2
This comment mentions that on Win 64bit cannot reproduce.
So, unless I am wrong we have a tier 2 platform case here, which (imo) would warrant a
P-high (or lower?) and/or a
any thoughts? cc: @Santiago Pastorino
we should answer the question if this is tier 1 or not
I'm tidying up the agenda so won't have the time to properly check this
@apiraino if we have doubts leave it as
P-critical and mention in the summary that is uncertain if it's tier 1 or 2
and in case it's tier 2 we should downgrade the priority
i686-windows-msvc 32bit right?
so I believe this is a Tier 2 case
I stand corrected,
i686-windows-msvc is still Tier 1
i686 is 32-bit, and it's Tier 1.
any progress here?
This was brought up in the last compiler meeting that actually took place (last week's didn't happen due to the holidays). pnkfelix mentioned that it hadn't been investigated yet and it was proposed to leave it for now since it's not a new regression and there were more pressing issues for the upcoming release: https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.20meeting.5D.202020-12-17.20.2354818/near/220257185