--- title: Triage meeting 2024-12-18 tags: ["T-lang", "triage-meeting", "minutes"] date: 2024-12-18 discussion: https://rust-lang.zulipchat.com/#narrow/channel/410673-t-lang.2Fmeetings/topic/Lang.20team.20day.202024-12-18 url: https://hackmd.io/oWnNDacQQhuECdrKgb0BEg --- # T-lang meeting agenda - Meeting date: 2024-12-18 ## Attendance - People: TC, tmandry, scottmcm, nikomatsakis, Josh ## Rust 2024 review ### Meta TC: We have tracking issues for the Rust 2024 aspects of every item queued for the edition: https://github.com/rust-lang/rust/issues?q=label%3AA-edition-2024+label%3AC-tracking-issue For each item, we've identified an *owner*. Our motivating priorities are: - Make this edition a success. - Do so without requiring heroics from anyone. - ...or stressing anyone or everyone out. The current timeline is: | Date | Version | Edition stage | |------------|---------------|--------------------------------| | 2024-11-28 | Release v1.83 | Stabilize Rust 2024 on master | | 2025-01-03 | Branch v1.85 | Cut Rust 2024 to beta | | 2025-01-09 | Release v1.84 | Announce Rust 2024 is pending! | | 2025-02-20 | Release v1.85 | Release Rust 2024 | Rust 2024 is stabilized now on nightly, and we've put out a call for testing the nightly beta: https://blog.rust-lang.org/2024/11/27/Rust-2024-public-testing.html All lang priority items are ready for Rust 2024. The remaining lang items just needing some documentation are: ## Nominated RFCs, PRs, and issues ### "change guarded string reserved tokens to `#"`, `##"`, `###`" rust#133924 **Link:** https://github.com/rust-lang/rust/pull/133924 TC: We'll close this. Meeting consensus: Ship the `##` reservation as-is. ### "Lint against `&T` to `&mut T` and `&T` to `&UnsafeCell<T>` transmutes" rust#128351 **Link:** https://github.com/rust-lang/rust/pull/128351 NM: The library construct is named after the language idea of what a transmute is. TC: Seeing that we're all agreed on that, we'll say that on the issue. ### "Specify the behavior of `file!`" rust#134442 **Link:** https://github.com/rust-lang/rust/pull/134442 TC: Seems we're all agreed; it's in FCP. ### "Stabilize `feature(trait_upcasting)`" rust#134367 **Link:** https://github.com/rust-lang/rust/pull/134367 TC: Niko proposed FCP merge. I've checked off. Reference PR: https://github.com/rust-lang/reference/pull/1622 TC: In discussion, it seems this Reference PR looks right to us, modulo some comments and questions that we've left, and Niko will leave a comment about the subtle safety vs validity point about a pointer with an invalid vtable (that it's valid, but it's unsafe, because you can't release it to safe code, as such code could safely observe the invalid vtable). ### "Add reference for asm-goto" **Link**: https://github.com/rust-lang/reference/pull/1693 TC: In discussion, this PR looks right to us.