# Backlog Bonanza 2022-05-11

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

Currently on page 5

## 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
* 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

Attendance: Felix, Scott, Josh, Mark

## Tracking issue for RFC 2294, "if let guard" #51114

https://github.com/rust-lang/rust/issues/51114

* known bugs, impl incomplete
* Likely missing tests in this area

## Tracking issue for the #[alloc_error_handler] attribute (for no_std + liballoc) #51540

https://github.com/rust-lang/rust/issues/51540

* Ongoing work in this area, in particular -Zoom-panic (driven by Amanieu)
* That work is heading in a different area and so may want to close this; it's not clear we want this feature in this form.

## Tracking issue for RFC 2397, "#[do_not_recommend]"

https://github.com/rust-lang/rust/issues/51992

Esteban's proposal for a more general thing:
https://internals.rust-lang.org/t/stable-diagnostic-affecting-attribute-with-unstable-api/16368?u=scottmcm

Scott to write comment.

## Tracking issue for RFC 2289, "Associated type bounds" #52662

https://github.com/rust-lang/rust/issues/52662

* Types team potentially? Josh to tag Niko in

## Tracking issue for comparing raw pointers in constants #53020

https://github.com/rust-lang/rust/issues/53020

* Unclear state (needs summary)
* Likely design concerns (runtime vs compile-time behavior)

## (Modules) Tracking issue for crate as a visibility modifier #53120

https://github.com/rust-lang/rust/issues/53120

* There are a bunch of design concerns
* ambiguity at syntax level
* lack of clear motivation for slightly shorter name at this point
* Work to re-add this under any name is fairly minimal
* fcp close now, with a future MCP etc if folks have strong push for a particular proposal

## Tracking issue for eRFC 2497, "if- and while-let-chains, take 2" #53667

https://github.com/rust-lang/rust/issues/53667

* https://github.com/rust-lang/rust/pull/94927
* S-ready-to-stabilize (ish)?

#[cfg(FALSE)]
fn f() {
    let x = (let y = 1);
}

* Josh tagging lang-nominated, and raising a concern on this question

## Tracking Issue: Procedural Macro Diagnostics (RFC 1566) #54140

https://github.com/rust-lang/rust/issues/54140

* proposed new API https://github.com/rust-lang/rust/pull/83363
* from https://github.com/rust-lang/rust/issues/54140#issuecomment-802701867
* https://github.com/rust-lang/rust/issues/54140#issuecomment-944675827
* proposal is to drop T-lang from the issue after some action indicating that T-lang has no particular stake in the API itself, but is OK with proc macros gaining the capability to emit diagnostics.

## tracking issue for infer_static_outlives_requirements (RFC 2093 spinoff) #54185

https://github.com/rust-lang/rust/issues/54185