Hi, after today's weekly meeting I was checking exactly which working groups are active and which aren't
and also checking the rotation
|Name||Status||Short Description||Zulip Stream|
|Async-await Implementation||Active||Implementing async-await||[#t-compiler/wg-async-await][async-await_stream]|
|LLVM||Incubating||Working with LLVM upstream to represent Rust in its development||[#t-compiler/wg-llvm][llvm_stream]|
|RFC 2229||Paused until 2020||Make a closure capture individual fields of the variable rather than the entire composite variable||[#t-compiler/wg-rfc-2229][rfc-2229-stream]|
|RLS 2.0||Active||Experimenting with a new compiler architecture tailored for IDEs||[#t-compiler/wg-rls2.0][rls20_stream]|
|Meta||Active||How compiler team organizes itself||[#t-compiler/wg-meta][meta_stream]|
|Non-Lexical Lifetimes (NLL)||Winding down||Implementing non-lexical lifetimes||[#t-compiler/wg-nll][nll_stream]|
|Traits||Active||Improving the trait-system design + implementation||[#t-compiler/wg-traits][traits_stream]|
|Parallel-rustc||Active||Making parallel compilation the default for rustc||[#t-compiler/wg-parallel-rustc][parallel-rustc_stream]|
|MIR Optimizations||Active||Write MIR optimizations and refactor the MIR to be more optimizable.||[#t-compiler/wg-mir-opt][mir-opt-stream]|
|Rustc pipelining||Active||Enable Cargo to invoke rustc in a pipelined fashion, speeding up crate graph compiles.||[#t-compiler/wg-pipelining][pipelining-stream]|
|Polonius||Active||Exploring the integration of the "NLL 2.0"-like ["Polonius analysis"][Polonius] into rustc||[#t-compiler/wg-polonius][polonius_stream]|
|Learning||Active||Make the compiler easier to learn by ensuring that rustc-dev-guide and api docs are "complete"||[#t-compiler/wg-learning][learning_stream]|
|Diagnostics||Active||Use crates.io crates for diagnostics rendering and make emitting diagnostics nicer.||[#t-compiler/wg-diagnostics][diagnostics_stream]|
|Polymorphization||Active||Implement an analysis to detect when functions can remain polymorphic during code generation.||[#t-compiler/wg-polymorphization][polymorphization_stream]|
|Profile-Guided Optimization||Retired||Implementing profile-guided optimization for rustc||[#t-compiler/wg-profile-guided-optimization][pgo_stream]|
is taht information accurate?
and also https://github.com/rust-lang/compiler-team/blob/b3fb6f89ac8bb1c3a526360b17bbc2f95d6a064d/layouts/shortcodes/checkin-schedule.html#L20-L24, that needs an update too
cc @nikomatsakis maybe you have more information that I do
I already know from today's meeting that Rustc pipelining is retired
I guess my question is a about LLVM is incubating?, RFC 2229 should say on pause until 2020, Polymorphization is active right?
and then we need to change Rustc pipelining to retired
LLVM is in permanent incubation state :slight_smile: Techincally we were semi-active at some point, less so nowadays, but I never got past all the red tape properly setting up the formal workgroup other than writing a small doc on that repo.
I'm working a lot on pattern matching features, and matthewjasper has helped out a ~bit~ substantially with or-patterns lowering
maybe that counts as wg-nll, but probably not?
there's some work regarding leak check and stuff, but I suppose that's wg-traits now
so yeah, nll is winding down
wg-diagnostics is sorta not really a working group in the sense that it meets and stuff
its mostly just a loose collection of folks who sometimes hack on diagnostics
we're not doing any projects as a group
I think it seems clear that both LLVM + Diagnostics are more "areas of the compiler" than working groups -- and I think that's fine! We should remove them from the list but we should just have this as a concept, I think. Honestly, NLL and probably traits would be good additions to the list. Maybe it'd be useful to try and breakdown a list of "compiler areas" where we could have dedicated chats? This seems related to expert map. It'd be nice to discuss things in terms of those "broad areas" (and perhaps have a map of "these directories correspond to that area")