I will be doing pre-triage in this channel.
first up: un-prioritized nominated issues. There are 8.
unpri nom 1/8: "thread 'rustc' panicked at 'called
Result::unwrap() on an
Err value: DistinctSources(DistinctSources" #66805
needs mcve. Going with P-high for this one for now (and removing nomination label).
P-medium, removing nomination label.
unpri nom 3/8: "Compiler panic while building crate with tokio, rocket, and snafu" #66787
P-high, removing nomination label
unpri nom 4/8: "Broken MIR ICE" #66768
ugh it looks like this is blossoming into a family of normalization related ICEs.
P-high, removing nomination label
unpri nom 5/8: "Regression in Error conversion from Infallible" #66757
reading over the comment thread here, i cannot immediately tell whether I need to rope T-lang into this issue (which is already tagged with T-compiler and T-libs) ...
at the very least it seems like we might need to hold off (again) on stabilizing
anyway, P-high. Leaving nominated.
unpri nom 6/8: "Closure type error" #66706
that's pretty fun
triage: P-high, removing nomination. tagging with const-eval.
unpri nom 7/8: "rustc crash on 1.39.0 stable with combination of
okay so the task here is high priority but easy: identify which PR on nightly fixed this and consider backporting it.
P-high, leaving nominated.
well, it really doesn't deserve to stay nominated. I'll just advertise it on the meeting channel.
unpri nom 8/8: "under latest MinGW, cannot link with C code using stdout" #47048
okay we started discussing what priority to give this last week, but then I switched topics to the WG-traits checkin
leaving nominated. maybe we can assign a priority today.
though perhaps I should write a comment with niko's summary. I'll do that now.
okay. I wrote a summary. And now I think I'll mark this P-high but remove nomination.
there are zero un-prioritized beta regressions
there is one un-prioritized nightly regression
unpri ν regr 1/1: "Broken MIR after compiler update when indexing statics with async values" #66695
has PR. Marking P-high.
next, a pass over the nominated issues to make sure there's no stale artifacts from last week.
we discussed "NLL Regressions in 1.40" #66517 last week. I'm going to self-assign it to try to push through the follow up work asynchronously.
ah, wait, we had agreed "I'm fine with tabling and coming back to it next week with a todo list" for #66517
(see also discussion in parallel wg-nll zulip topic )
Okay that covers all the issues that we looked at last week, I think.
(at least ones where I would feel comfortable removing the I-nominated tag)
looking over the P-high issues now, mainly to try to identify issues that we could downgrade to P-medium or close.
@centril regarding " improper_ctypes fires for &mut T, &T, *const T and *mut T (when T: Sized)" #66220, can I remove the I-nominated tag there? Or is that something you think still needs (more) discussion in T-lang meeting?
downgrading "The compiler should report publicly exported type names if possible" #21934 to P-medium. It got attention, that was good, but that doesn't mean it should stay P-high.
looking at "Miscompilation with target-cpu=znver1 (AMD Ryzen 1000/2000 series) on Windows + LLVM 9." #63959; tempted to downgrade to P-medium (as "just an LLVM bug"). Posted question on parallel zulip topic.
okay, I think now I'll start preparing a hackmd agena for today.