Hey @T-compiler/WG-meta -- anybody around to meet?
It might just be me
@pnkfelix, are you on the above user group btw?
So I was thinking that a good next goal would be to create the "reducer and bisector" ICE-breaker
I think at this point the main blocker, which was @Santiago Pastorino's work on
cargo bisect-rustc, is done
maybe it's a good idea to setup a checklist
(I believe I am not on WG-meta, not yet at least. Probably should join.)
tmandry was asking recently about reduction tools
I'm looking over the list of issues
I think that https://github.com/rust-lang/compiler-team/issues/174 -- which was for the LLVM group
can presumably be closed
but it provides a good "checklist" starting point I guess
we need to update our compiler-team page to drive attention to these groups as a way to contribute
this work item never got done I guess
What should we call it? "Cleanup ICE-breakers"? "Bisect-and-reduce ICE-breakers"?
I can't come up with something obvious
Nothing springs to mind here.
I know it's a tough one
there has to be some kind of funny name :P
maybe just "cleanup crew"
it has that "team feeling"
which has a checklist
I'm going to use the next ten minut to work on that first item
First draft of a guide: https://github.com/rust-lang/rustc-guide/pull/556
Updated https://github.com/rust-lang/rustc-guide/pull/556 with a bit more
It all reads well to me.
Hey @DPC -- it'd be good to discuss at some point the release team triage wg and the compiler triage efforts and if/how it makes sense to "join forces". One thing we're thinking of doing is creating a "cleanup crew" that is aimed at minimizing and bisecting bugs, which seems pretty related (see above :point_up: for more notes)