---
# System prepended metadata

title: Backlog Bonanza 2021-11-10

---

# Backlog Bonanza 2021-11-10

[GitHub query](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AC-tracking-issue+label%3AT-lang)

## omg what are we doing

* Take things that have been unstable for a while and "disposition them".
* Goal: Everything that is nightly only has one or more of the following labels, indicating the blocker(s) to stabilizing it:
    * S-tracking-ready-to-stabilize: Needs a stabilization PR (good to go :train:)
    * S-tracking-needs-to-bake: Needs time to bake (set a date? other criteria?)
    * S-tracking-impl-incomplete: Not code complete or blocking bugs
        * B-rfc-implemented? I've never understood this
    * S-tracking-unimplemented: Implementation not begun
    * S-tracking-design-concerns: Blocking design concerns
        * This might be "doesn't quite seem to deliver value we hoped for" or "something doesn't feel right"
    * S-tracking-perma-unstable
        * Internal implementation detail of rustc, stdlib
    * S-tracking-needs-investigation
        * 
    * And now we bikeshed!!!
        * what color????
        * #4682b4 [color picker](https://www.google.com/search?q=4682b4+color&client=firefox-b-1-d&sxsrf=AOaemvKFOKyg9PknGiCgIRDeehHX8p2amg%3A1636568155008&ei=WwyMYegD4NfK0w_oiL6oBg&oq=4682b4+color&gs_lcp=Cgdnd3Mtd2l6EAMyBQgAEIAEMgUIABCABDIGCAAQFhAeMgYIABAWEB4yBggAEBYQHjIGCAAQFhAeMgYIABAWEB46BwgjELADECc6BwgAEEcQsAM6BwgAELADEEM6BAgAEB5KBAhBGABQ5gJYzQdgnAhoAXACeACAAVCIAaEDkgEBNpgBAKABAcgBCsABAQ&sclient=gws-wiz&ved=0ahUKEwionZ68s470AhXgq3IEHWiED2UQ4dUDCA0&uact=5)
* 

##  Tracking issue for inherent associated type. #8995 

[#8995](https://github.com/rust-lang/rust/issues/8995)

* S-tracking-unimplemented

##  Tracking Issue for auto traits (auto_traits) -- formerly called opt-in built-in traits (optin_builtin_traits) #13231 

* semver train wreck :)
* S-tracking-perma-unstable
* Wonder of wonders, we have a design note!
    * https://lang-team.rust-lang.org/design_notes/auto_traits.html

## Tracking issue for RFC 66 #15023

* Just close the issue with a comment
    * We still think this is a good idea but it's so stale that we would want to start fresh

##  Tracking issue for stmt_expr_attributes: Add attributes to expressions, etc.  #15701

* We have attributes on statements, but not expressions
* We don't know what is the status?!
* Seems like it has design concerns, it may be as implemented as we want it
* Needs investigation
    * [something like this](https://github.com/rust-lang/rust/issues/18469#issuecomment-61578672)

## Implement revised coercion rules #18469

* [summary comment](https://github.com/rust-lang/rust/issues/18469#issuecomment-61578672)
* impl incomplete

## 

* before stabilizing we would need a good summary of current state, concerns

## likely/unlikely intrinsics #26179

* has been implemented...do they...work?
* these days, with LLVM you can get more fine-grained information, esp. with PGO
* S-ready-for-stabilization
* [hsivonen commented](https://github.com/rust-lang/rust/issues/26179#issuecomment-357175153)
* maybe this wants to be called `std::hint::likely`?
    * that's a libs decision
* conclusion: tag as T-libs-api to bikeshed the name and T-compiler to check on "commitment"
* from a lang perspective: this is an impl hint that the compiler may or may not choose to respect
    * 

## tracking issue for DST coercions #27732

* this seems like needs summary, we're not sure where we're at

## tracking issue for const prop not causing add'l errors #28238

* we think this is done, nominate for oli to see if we can close?
* I-needs-summary, if it's not just close, then don't know what's left

## Nonparametric dropck (tracking issue for RFC 1238) #28498

* this was added as a stopgap, to stabilize, it needs some design work to decide what it's eventual shape should be
* I-design-concerns

## Tracking issue for `#[thread_local]` stabilization #29594

* [representative comment](https://github.com/rust-lang/rust/issues/29594#issuecomment-549056545)
* design concerns, unclear if we want it, though we might

## Tracking issue for plugin stabilization (plugin, plugin_registrar features) #29597

* nominate to assess if it should be removed?
* is anything using it?
* I-compiler-nominated, T-compiler

## Tracking issue for log_syntax, trace_macros #29598

* does this still exist?
* yes! this is for debugging. design concerns. seems like a problem, no idea if this is the thing we would want. (prob not)

## Tracking issue for concat idents #29559

* doesn't do the thing people want, which is to use it as an ident
* I-design-concerns -- doesn't do what people want, maybe not workable
* 