# Backlog of T-compiler issues

[Query](https://github.com/rust-lang/compiler-team/issues/?q=is%3Aissue+state%3Aopen+sort%3Acreated-asc)

<details><summary>previously closed</summary>

- Candidates for immediate closing:
- "compiler-team twitter account" [compiler-team#192](https://www.github.com//rust-lang/compiler-team/issues/192)
- "clickable section headers" [compiler-team#172](https://www.github.com//rust-lang/compiler-team/issues/172)
- "Add compiler triage meeting procedure to procedures directory" [compiler-team#163](https://www.github.com//rust-lang/compiler-team/issues/163)
- "Triage meeting notes after 2019-06-20 don't appear on sidebar" [compiler-team#153](https://www.github.com//rust-lang/compiler-team/issues/153)
- "fill in directories for experts.toml file" [compiler-team#87](https://www.github.com//rust-lang/compiler-team/issues/87)
- (we don't store an expert map anymore)
- "add some form of "subtitle" for team contributors and members" [compiler-team#64](https://www.github.com//rust-lang/compiler-team/issues/64)
- "Document best practices for working groups" [compiler-team#61](https://www.github.com//rust-lang/compiler-team/issues/61)
- "migrate our procedures and other policy content to rust-forge" [compiler-team#204](https://www.github.com//rust-lang/compiler-team/issues/204)
- "Add contributing section?" [compiler-team#208](https://www.github.com//rust-lang/compiler-team/issues/208)
- "todo: devise concrete plan for revamping our maintenance/triage processes" [compiler-team#239](https://www.github.com//rust-lang/compiler-team/issues/239)
- "document what team membership means, responsibilities, and how to adjust" [compiler-team#248](https://www.github.com//rust-lang/compiler-team/issues/248)
- "Create Diagnostics ICE-breaker group" [compiler-team#283](https://github.com/rust-lang/compiler-team/issues/283) and [compiler-team#309](https://github.com/rust-lang/compiler-team/issues/309)
- Ping group not active but maybe a good idea? (see recent [Zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Are.20icebreakers-.7Bllvm.2Ccleanup-crew.7D.20still.20active.2Fused.3F/near/506919611))
- "Revive incremental compilation working group" [compiler-team#299](https://github.com/rust-lang/compiler-team/issues/299)
- WGs are phased out
- "Missing words in 5/29 roadmap post" [compiler-team#327](https://github.com/rust-lang/compiler-team/issues/327)

</details>

- "Bring existing compiler team repositories up-to-code." [compiler-team#65](https://www.github.com//rust-lang/compiler-team/issues/65)
- discussed with team leads, worked on by @_**apiraino**
- "Investigate ways to announce compiler team updates." [compiler-team#62](https://www.github.com//rust-lang/compiler-team/issues/62)
- discussed with team leads (also w.r.t. increase involvement of team members). We have social media channels.
- anything specific we might want to announce? (ex. a special mention for a bump in perf.)
- "mentorship/internship program" [compiler-team#56](https://www.github.com//rust-lang/compiler-team/issues/56)
- Idea per se is good but how could this look like? Who has the capacity to initiate and follow up on this? Maybe talk with the Council/Foundation?
- Or just close?
- "What is the process to add a compiler flag?" [compiler-team#261](https://www.github.com//rust-lang/compiler-team/issues/261)
- I think documented [here](https://forge.rust-lang.org/compiler/proposals-and-stabilization.html)
- "Compiler areas, working groups and expert map" [compiler-team#264](https://www.github.com//rust-lang/compiler-team/issues/264)
- @_**apiraino**: I would probably salvage the "expert map" part which was on my radar (low priority, though)
- Or just close?
- "Compiler Feature Backlog Bonanza" [compiler-team#484](https://github.com/rust-lang/compiler-team/issues/484)
- It's ongoing
- "Parallel compilation support strategy" [compiler-team#492](https://github.com/rust-lang/compiler-team/issues/492)
- Asked in #**t-compiler/parallel-rustc>Parallel compilation strategy**
- "Dealing with disabled tests" [compiler-team#540](https://github.com/rust-lang/compiler-team/issues/540)
- Meeting scheduled on 11st, April
- "Revisit MIR opt levels" [compiler-team#579](https://github.com/rust-lang/compiler-team/issues/579)
- Marked as "help wanted"
- "Retire the mailing list and make all decisions on zulip" [compiler-team#649](https://github.com/rust-lang/compiler-team/issues/649)
- The MCP is stale since long, there's an [open concern](https://github.com/rust-lang/compiler-team/issues/649#issuecomment-1618902660) I'd like to work on ([see my comment](https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/Retire.20the.20mailing.20list.20and.20make.20all.20deci.E2.80.A6.20compiler-team.23649/near/398510850), but clearly low priority)
- "Add hygiene attributes to compile expanded source code" [compiler-team#692](https://github.com/rust-lang/compiler-team/issues/692)
- waiting on seconding, pinged [recently](https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/Add.20hygiene.20attributes.20to.20compile.20expande.E2.80.A6.20compiler-team.23692/near/503057625)
- "Policy change around adding new unstable flags" [compiler-team#787](https://github.com/rust-lang/compiler-team/issues/787)
- waiting on seconding, pinged [recently](https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/Add.20hygiene.20attributes.20to.20compile.20expande.E2.80.A6.20compiler-team.23692/near/503057625)
- "Tracking Issue for the WASM | WASI | Emscripten notification groups" [compiler-team#799](https://github.com/rust-lang/compiler-team/issues/799)
- This is waiting on a blog post announcement. Unsure if it was ever written.
- Maybe close?
- Related question: why a Zulip stream *must* be part of the creation of a notification group? I removed [recently](https://github.com/rust-lang/rust-forge/commit/bd79d1d786c7b38151cb764dd753b24c56e48cc4#diff-209c0b180fa706620adc67cda8c76209154c0e282150238ee63dd5ecc29b6121L20-L21) from the documentation a notice about that: I don't think it's really necessary?
- "Pruning stale compiler team proposals" [compiler-team#821](https://github.com/rust-lang/compiler-team/issues/821)
- doing right now :)

These are recently opened and still being discussed:
- "Rename "dylib" crate type to "rdylib" (keep old name but deprecate it), and maybe do the same for "staticlib" → "cstaticlib"" [compiler-team#825](https://github.com/rust-lang/compiler-team/issues/825)
- "Add `-C hint-mostly-unused` option" [compiler-team#829](https://github.com/rust-lang/compiler-team/issues/829)
- "`rustc_target` for rust-analyzer" [compiler-team#839](https://github.com/rust-lang/compiler-team/issues/839)
- "Basic target naming rules" [compiler-team#850](https://github.com/rust-lang/compiler-team/issues/850)
- "Add one more "late metadata"/"digest" file to rlib archives" [compiler-team#853](https://github.com/rust-lang/compiler-team/issues/853)