@nikomatsakis @pnkfelix there are 14 open regression issues, 12 of them marked T-compiler
and the release is in a bit more than 2 weeks :/
I’ll try to go through these on my own tomorrow, in order to figure out which ones need to be subjects at the T-compiler meeting on Thursday
(Luckily I am not at the All-Hands so I can actually commit to such a task)
I'm going to just close https://github.com/rust-lang/rust/pull/59858 outright because I don't see the language team accepting this back.
Is that the correct link? It goes to a months old PR for me.
@davidtwco oops; I meant https://github.com/rust-lang/rust/issues/61481
I just realized I should probably be logging my actions on these issues somewhere
so lets see
"ICE while bootstrapping (./x.py build)" #59945 -- I closed this yesterday as "not enough information to reproduce nor act."
"regression: overflow evaluating, Send/Sync?" #61472 -- I confirmed that fuzzy-pickles and conch-runtime were resolved on nightly at approx same time that PR #61754 landed. I have also nominated PR #61754 for a beta backport
"regression: conflicting implementation for &_" #61473 -- closed as "fixed by upstream crate patches", as in,
cargo update should suffice. (Maybe crater should include this as something it automatically attempts?)
"regression: conflicting implementations for From<&_>" #61474 -- closed as "fixed by upstream crate update". But in this case, I don't think
cargo update suffices for the fix, because the upstream update was not a patch release.
"regression: trait no longer implemented" #61563 -- posted a lot a comments in the issue. Basically this was a subtle issue of a previously untested doc example that started being tested and thus exposed code that does not compile. Filed an issue with the originating crate and closed as not-a-bug.
Layout mismatch when copying! from macro" #61663 -- very very weird; see comments on issue. Bisected injection down to PR #59560. assigned to @Matthew Jasper and self. Removed nomination tag.
I'm reading it ever since you wrote which PR caused it (I reviewed it after all)
The only entry point I have so far is that enum discriminant computations are always confusing to me since everything is
isize until actually used