---
title: Triage meeting 2025-07-23
tags: ["T-lang", "triage-meeting", "minutes"]
date: 2025-07-23
discussion: https://rust-lang.zulipchat.com/#narrow/channel/410673-t-lang.2Fmeetings/topic/Triage.20meeting.202025-07-23/
url: https://hackmd.io/k3lwzzlqQE-S5F7T3vNiJw
---
# T-lang meeting agenda
- Meeting date: 2025-07-23
## Attendance
- People: TC, tmandry, Josh, Niko, Scott, eholk, Tomas, Taylor
## Meeting roles
- Driver: TC
- Minutes: Tomas Sedovic
## Scheduled meetings
- 2025-07-23: "Design meeting:Named macro capture groups" [#339](https://github.com/rust-lang/lang-team/issues/339)
- 2025-07-30: "Design meeting: In-place Initialization" [#332](https://github.com/rust-lang/lang-team/issues/332)
Edit the schedule here: https://github.com/orgs/rust-lang/projects/31/views/7.
## Announcements or custom items
(Meeting attendees, feel free to add items here!)
### Guest attendee items
TC: For any guests who are present, please note in this section if you're attending for the purposes of any items on (or off) the agenda in particular.
### Moving right along
TC: As we've been doing recently, due to the impressive backlog, I'm going to push the pace a bit. If it's ever too fast or you need a moment before we move on, please raise a hand and we'll pause.
### Design meeting at 12:30 EST / 09:30 PST / 17:30 CET
TC: Remember that we have a design/planning meeting that starts half an hour after this call ends.
### Next meeting with RfL
We're next meeting with RfL on 2025-04-23 to review the status of RfL project goals.
https://github.com/rust-lang/rfcs/pull/3614
## Rust 2025 review
### Meta
TC: We should start thinking about Rust 2025.
Our motivating priorities are:
- Make every edition a success.
- Do so without requiring heroics from anyone.
- ...or stressing anyone or everyone out.
The tentative timeline will be:
| Date | Version | Edition stage |
|------------|---------------|--------------------------------|
| 2025-04-03 | Release v1.86 | Checking off items... |
| 2025-05-15 | Release v1.87 | Checking off items... |
| 2025-06-26 | Release v1.88 | Checking off items... |
| 2025-08-07 | Release v1.89 | Checking off items... |
| 2025-09-12 | Branch v1.91 | Go / no go on all items |
| 2025-09-18 | Release v1.90 | |
| 2025-10-24 | Branch v1.92 | Stabilize Rust 2025 on nightly |
| 2025-10-30 | Release v1.91 | Rust 2025 nightly beta |
| 2025-12-05 | Branch v1.93 | Cut Rust 2025 to beta |
| 2025-12-11 | Release v1.92 | Announce Rust 2025 is pending |
| 2026-01-22 | Release v1.93 | Release Rust 2025 |
None.
## Nominated RFCs, PRs, and issues
### "[WIP] Forbid object lifetime changing pointer casts" rust#136776
**Link:** https://github.com/rust-lang/rust/pull/136776
TC: This was one thing holding up arbirtrary self types and derive coerce pointee. We had asked for some things that seem to be here now. Alice renominated it for us on that basis.
Niko: Sounds like we should do it.
Josh: Do we have an equivalent of the stabilization report or a draft release note explaining precisely what change is being made?
Josh: The description in the tracking issue gives an idea of the nature of the change: https://github.com/rust-lang/rust/issues/141402
TC: Probably want an update for the Reference too.
Josh: Agreed reference update is a good idea. We also need to make sure all the crates that could potentially break get a fix. Sounds like `may` and `metrics` got fixed.
TC: The issue has a long list of PRs that were put in. We did all we could.
TC proposed an FCP.
### "Mark all deprecation lints in name resolution as deny-by-default and report-in-deps" rust#143929
**Link:** https://github.com/rust-lang/rust/pull/143929
TC: petrochenkov wants to take four things (one deny-by-default, three warn-by-default). Macros expand from left to right and top to bottom. This was a number of violations of that and some violations of visibility with respect of macros. I've proposed FCP merge.
TC: Towards the bottom are the links to the docs for all the lints: https://github.com/rust-lang/rust/pull/143929#issuecomment-3105265710
Josh: I agree with the comment saying there should be a tracking issue for these.
Josh: Another item that may be topical:
https://github.com/rust-lang/rust/issues/79813
Josh: We used to accept macros that expand to expressions and yet expand to a semicolon. This seems to be a blocker for some aspects of how macros are implemented, affecting how `macro_rules!` macros use the `LegacyBang` mechanism.
Josh: I wonder if it might be around time to escalate to deny-by-default and report-in-deps (if it's not already report-in-deps).
Josh: All of these seem like they're ready to ship.
TC: I've proposed FCP, and we're now in FCP.
### "Tracking Issue for denying trailing semicolons in expression macro bodies" rust#79813
**Link:** https://github.com/rust-lang/rust/issues/79813
TC: No PR here so our take-away here is to make a request.
Josh: I'd be happy to make the PR. Do we think this has progressed far enough to be able to do deny-by-default. It's been introduced at least in 2020 if not earlier. It's been deprecated for a long time. It is warn-in-deps and has been for a while.
TC: There's a future incompatibility warning and warn in deps. I'm in favor of switching this to deny-by-default.
Josh: We have a whole mechanism for function-style macros that transform tokens-to-tokens, for proc macros. And here also are the `macro_rules!` macros that use `LegacyBang` that generate AST, and among other things use that to see that they're in expression context and handle the incorrect semicolon. So this would allow for a fair bit of cleanup.
Tyler: Deny by default sounds fine to me.
### "stabilize c-style varargs for system, sysv64, win64, efiapi, aapcs" rust#144066
**Link:** https://github.com/rust-lang/rust/pull/144066
Josh: This is c-style varags in terms of declaring an external function that accepts C-style varargs. Not defining a function that accepts them. For being able to call external functions.
Josh: The question is whether `extern "system"` should use vararg support. And the ussie is that `system` uses a differen ABI on different systems.
Scott: (Was confused and thought this was the implementing varargs thread.)
Josh: This is stable for C already and has been for a while.
Josh: I'm currently trying to double-check an assumption on microsoft compiler that varags on stdcall is just varags for C.
Josh: Do we have a warning that says "you're trying to use varargs with `stdcall` so you must switch to `system`"? I don't think we do.
Josh: On MSVC if you write stdcall, you normally get the stdcall calling convention. But if you write stdcall and use varargs, it will use the C ABI and ignore stdcall.
Josh: We rejected stdcall being magic and introduced "system" instead: https://github.com/rust-lang/rust/issues/137018.
Josh: This proposal suggests adding vararg support for "system". And I'm suggesting that we should notice if you're trying to use varargs on MSVC and suggest to switch to C in that case. I'll write a comment saying this.
Tyler: Sounds there are unresolved questions.
Josh: I think it's good enough for FCP and file a concern for the discussion to settle (and/or have people ask us to block it).
Tyle: It sounds like Jubilee has some concerns and wants to consider more of these things together and has'nt written them down yet.
Josh: One of the things in the back-and-forth discussion was someone saying that they're in no rush giveng that lang won't get around to it any time yet. So posting something like "we're ready to start an FCP" to signal that we'll look into this when ready.
### "const-eval: full support for pointer fragments" rust#144081
**Link:** https://github.com/rust-lang/rust/pull/144081
TC: We had a long discusssion about an earlier stabilization that had a weird limitation. RalfJ was able to resolve this limitation:
> This PR implements the logic to properly track how those individual bytes relate to the original pointer, and to recognize when they are in the right order again.
TC: Impressive work, looks good to me. I proposed FCP merge.
Josh: So this pulls out upper and lower parts of the pointers,
Scott: If you have unaligned pointers in a packed struct and you do chunked ?? for copying. There was a previous discussion about `swap_nonoverlaping` method we wanted to stabilize where we had have a special CTFE path. And now we'll be able to drop this.
Niko: I'm all for this though I think it demonstrates a gap for us where I'd like us to be developing a shared mental model for what's happening in const-eval. This sounds like we can chunk an address into bytes and build an address out of them.
Scott: Everything I've said so far is in the abstract without looked into it in detail.
Niko: I'll mark it for review and follow up with Ralf. But this sounds like a-mir-formality could help us improve the sharde understanding.
Tyler: It seems that there are cases where if we want to check provenance, we may have to track them per byte.
Tyler: The reasons we might not to do this would be the performance of const-eval, complexity of the spec.
Niko: I think this will go into spec eventually. We'll need to be able to say how does the compiler run Rust code.
Scott: If you didn't implement this and let it pass through, would it impact a must-diagnose case?
Niko: You mean, if you added a different compiler?
Scott: I was wondering, given perf implications. If we said "my CTFE is not capable of putting the provenance back together", could we do that?
Niko: I don't know, that's a good question. If you don't want to catch all the errors, but you want just compile the program, right?
TC: Scott can you please write that up on the issue? I'm curious to see RalfJ's reply to that.
Scott: Yes.
TC: We're in FCP.
Tyler: I want to raise a concern on spec complexity. Also working out whether a conforming implementation needs to find these violations or not. I'm not expecting to block this in perpetuity, but I'd like to hear that answered.
### "Stabilize const TypeId::of" rust#144133
**Link:** https://github.com/rust-lang/rust/pull/144133
TC: We previously thought about const stabilizing TypeId::of. We couldn't stabilize `PartialEq` for it in const. They made it impossible by adding provenance on TypeId in const. You can't poke at it in const. You can't `eq` it in const yet but we want to add that later.
TC: We're in FCP.
### "Add lint against dangling pointers from local variables" rust#144322
**Link:** https://github.com/rust-lang/rust/pull/144322
TC: GitHub put up a tool called "codeQL" -- it's a multi-language linter. They added Rust support a couple weeks ago. They had a set of prebuilt lints that matched to the common weaknesses database. I was looking through their lints. I found one where we don't lint the case and it's this one. Urgau was surprised we didn't lint this either and so submitted a PR.
TC: I proposed an FCP.
Josh: How much tracking does this lint do?
```rust!
// This gets a warning
fn f() -> *const u8 {
let x = 0;
&x // returns a dangling ptr to `x`
}
// Does this get a warning?
fn f() -> *const u8 {
let x = 0;
let rx: &u8 = &x;
rx // returns a dangling ptr to `x`
}
```
Tyler: If it were implemented in MIR it would probably the more extended version, but it's not.
Josh: It's clearly an improvement and we sholud do it.
TC: We're in FCP.
### "lower pattern bindings in the order they're written and base drop order on primary bindings' order" rust#143764
**Link:** https://github.com/rust-lang/rust/pull/143764
Tyler: Diane has been working with Nadrieril about this. Diane found a number of ??. We've approved earlier fixes.
TC: This comes from https://github.com/rust-lang/rust/issues/142163. We agreed this is a bug and solicited a crater run and a PR. The crater run is done, the breakages are unrelated. Looks like we can break this.
Tyler: We agreed the existing behaviour was a bug although something very unlikely someone would notice.
Josh: Yeah. It's difficult to notice this but all the more reason to make it obvious.
Niko: I think we should do this. How much is this documented in the Reference?
TC: I was having the same thought. We should double-check the Reference on this and try to find a way to document this.
TC: FCP is up.
Niko: What does checking the box mean here?
TC: I'm looking at the tests. But to some degree I'm taking dianne's word that she did the thing we agreed to in the issue.
Niko: We want drops to appear in the relative order of when each binding first appears. Okay, that's what we're approving.
Scott: That sounds like a great summary to have when it's time to write the release notes that link to this.
Niko: My ideal would be for the Reference to give like three principles that cover cases like this one.
TC: +1.
TC: We're in FCP.
### "Stabilize `offset_of_enum`" rust#143954
**Link:** https://github.com/rust-lang/rust/pull/143954
TC: We discussed this last week and at the design meeting. The next step is probably to talk about what we want to do with respect to e.g. `try_offset_of_enum`. But that's for another day.
(The meeting ended here.)
---
### "Stabilize the `breakpoint` function" rust#142325
**Link:** https://github.com/rust-lang/rust/pull/142325
## On radar RFCs, PRs, and issues
### "Fallback `{float}` to `f32` when `f32: From<{float}>` and add `impl From<f16> for f32`" rust#139087
**Link:** https://github.com/rust-lang/rust/pull/139087
### "Tracking issue for `cfg_select` (formerly `cfg_match`)" rust#115585
**Link:** https://github.com/rust-lang/rust/issues/115585
### "Split elided_lifetime_in_paths into finer-grained lints" rust#120808
**Link:** https://github.com/rust-lang/rust/pull/120808
### "Arbitrary self types v2: stabilize" rust#135881
**Link:** https://github.com/rust-lang/rust/pull/135881
### "Stabilize return type notation (RFC 3654)" rust#138424
**Link:** https://github.com/rust-lang/rust/pull/138424
### "`#[target_feature]` mismatch on unsafe trait fn vs its impl causes sneaky UB" rust#139368
**Link:** https://github.com/rust-lang/rust/issues/139368
### "Spurious irrefutable_let_patterns warning with let-chain" rust#139369
**Link:** https://github.com/rust-lang/rust/issues/139369
### "Stabilize `fn_align`: `#[align(N)]` on functions" rust#140261
**Link:** https://github.com/rust-lang/rust/pull/140261
### "`core::marker::NoCell` in bounds (previously known an `Freeze`)" rfcs#3633
**Link:** https://github.com/rust-lang/rfcs/pull/3633
### "Unsafe derives and attributes" rfcs#3715
**Link:** https://github.com/rust-lang/rfcs/pull/3715
### "[RFC] Allow packed types to transitively contain aligned types" rfcs#3718
**Link:** https://github.com/rust-lang/rfcs/pull/3718
### "RFC: Add an attribute for raising the alignment of various items" rfcs#3806
**Link:** https://github.com/rust-lang/rfcs/pull/3806
### "Tracking issue for RFC 2523, `#[cfg(version(..))]`" rust#64796
**Link:** https://github.com/rust-lang/rust/issues/64796
### "Tracking issue: Support for pointers with `asm_const`" rust#128464
**Link:** https://github.com/rust-lang/rust/issues/128464
### "lexer: Treat more floats with empty exponent as valid tokens" rust#131656
**Link:** https://github.com/rust-lang/rust/pull/131656
### "An unsafe const fn being used to compute an array length or const generic is incorrectly described as being an "item"." rust#133441
**Link:** https://github.com/rust-lang/rust/issues/133441
### "Stabilize `derive(CoercePointee)`" rust#133820
**Link:** https://github.com/rust-lang/rust/pull/133820
### "experiment with relaxing the orphan rule" rust#136979
**Link:** https://github.com/rust-lang/rust/issues/136979
### "Tracking issue for unsupported_calling_conventions (cdecl, stdcall, fastcall)" rust#137018
**Link:** https://github.com/rust-lang/rust/issues/137018
### "Oddity with lifetime elision and type aliases" rust#140611
**Link:** https://github.com/rust-lang/rust/issues/140611
### "Add `core::ptr::assume_moved`" rfcs#3700
**Link:** https://github.com/rust-lang/rfcs/pull/3700
### "#[deprecated] lint doesn't trigger when overriding deprecated method" rust#98990
**Link:** https://github.com/rust-lang/rust/issues/98990
### "Tracking Issue for unicode and escape codes in literals" rust#116907
**Link:** https://github.com/rust-lang/rust/issues/116907
### "sanitizers: Stabilize AddressSanitizer and LeakSanitizer for the Tier 1 targets" rust#123617
**Link:** https://github.com/rust-lang/rust/pull/123617
### "Built-in attributes are treated differently vs prelude attributes, unstable built-in attributes can name-collide with stable macro, and built-in attributes can break back-compat" rust#134963
**Link:** https://github.com/rust-lang/rust/issues/134963
### "Decide on behavior of `anonymous_lifetime_in_impl_trait`" rust#137575
**Link:** https://github.com/rust-lang/rust/issues/137575
### "[RFC] Add `#[export_ordinal(n)]` attribute" rfcs#3641
**Link:** https://github.com/rust-lang/rfcs/pull/3641
### "RFC: No (opsem) Magic Boxes" rfcs#3712
**Link:** https://github.com/rust-lang/rfcs/pull/3712
### "Tracking Issue: Procedural Macro Diagnostics (RFC 1566)" rust#54140
**Link:** https://github.com/rust-lang/rust/issues/54140
### "Tracking Issue for enum access in offset_of" rust#120141
**Link:** https://github.com/rust-lang/rust/issues/120141
### "Remove unstable cfg `target(...)` compact feature" rust#130780
**Link:** https://github.com/rust-lang/rust/pull/130780
### "Strengthen the follow-set rule for macros" rust#131025
**Link:** https://github.com/rust-lang/rust/issues/131025
### "Warn about C-style octal literals" rust#131309
**Link:** https://github.com/rust-lang/rust/pull/131309
### "Add lint against (some) interior mutable consts" rust#132146
**Link:** https://github.com/rust-lang/rust/pull/132146
### "RFC: Improved State Machine Codegen" rfcs#3720
**Link:** https://github.com/rust-lang/rfcs/pull/3720
### "Add `must-use-output` attribute" rfcs#3773
**Link:** https://github.com/rust-lang/rfcs/pull/3773
### "Effective breakage to `jiff` due to `ambiguous_negative_literals`" rust#128287
**Link:** https://github.com/rust-lang/rust/issues/128287
### "Simplify lightweight clones, including into closures and async blocks" rfcs#3680
**Link:** https://github.com/rust-lang/rfcs/pull/3680
### "Macro fragment fields" rfcs#3714
**Link:** https://github.com/rust-lang/rfcs/pull/3714
### "Add `homogeneous_try_blocks` RFC" rfcs#3721
**Link:** https://github.com/rust-lang/rfcs/pull/3721
### "Elided lifetime changes in `rust_2018_idioms` lint is very noisy and results in dramatically degraded APIs for Bevy" rust#131725
**Link:** https://github.com/rust-lang/rust/issues/131725
### "Coercing &mut to *const should not create a shared reference" rust#56604
**Link:** https://github.com/rust-lang/rust/issues/56604
### "#[cold] on match arms" rust#120193
**Link:** https://github.com/rust-lang/rust/pull/120193
### "`is` operator for pattern-matching and binding" rfcs#3573
**Link:** https://github.com/rust-lang/rfcs/pull/3573
### "Unsafe fields" rfcs#3458
**Link:** https://github.com/rust-lang/rfcs/pull/3458
### "RFC: Allow symbol re-export in cdylib crate from linked staticlib" rfcs#3556
**Link:** https://github.com/rust-lang/rfcs/pull/3556
### "Hierarchy of Sized traits" rfcs#3729
**Link:** https://github.com/rust-lang/rfcs/pull/3729
### "Language vs. implementation threat models and implications for TypeId collision resistance" rust#129030
**Link:** https://github.com/rust-lang/rust/issues/129030
### "RFC: inherent trait implementation" rfcs#2375
**Link:** https://github.com/rust-lang/rfcs/pull/2375
### "Raw Keywords" rfcs#3098
**Link:** https://github.com/rust-lang/rfcs/pull/3098
### "RFC: Implementable trait aliases" rfcs#3437
**Link:** https://github.com/rust-lang/rfcs/pull/3437
### "Should Rust still ignore SIGPIPE by default?" rust#62569
**Link:** https://github.com/rust-lang/rust/issues/62569
### "types team / lang team interaction" rust#116557
**Link:** https://github.com/rust-lang/rust/issues/116557
### "Trait method impl restrictions" rfcs#3678
**Link:** https://github.com/rust-lang/rfcs/pull/3678
### "Closing issues relevant to T-lang on this repo" rfcs#3756
**Link:** https://github.com/rust-lang/rfcs/issues/3756
### "Implement `PartialOrd` and `Ord` for `Discriminant`" rust#106418
**Link:** https://github.com/rust-lang/rust/pull/106418
### "Fallout from expansion of redundant import checking" rust#121708
**Link:** https://github.com/rust-lang/rust/issues/121708
### "What are the guarantees around which constants (and callees) in a function get monomorphized?" rust#122301
**Link:** https://github.com/rust-lang/rust/issues/122301
### "Policy for lint expansions" rust#122759
**Link:** https://github.com/rust-lang/rust/issues/122759
### "Decide on path forward for attributes on expressions" rust#127436
**Link:** https://github.com/rust-lang/rust/issues/127436
### "`continue` expressions in loop conditions" rust#118673
**Link:** https://github.com/rust-lang/rust/issues/118673
### "Tracking Issue for `breakpoint` feature (`core::arch::breakpoint`)" rust#133724
**Link:** https://github.com/rust-lang/rust/issues/133724
### "`fn_cast!` macro" rust#140803
**Link:** https://github.com/rust-lang/rust/issues/140803
### "Permit duplicate imports" rust#141043
**Link:** https://github.com/rust-lang/rust/pull/141043
### "Stabilize `if let` guards (`feature(if_let_guard)`)" rust#141295
**Link:** https://github.com/rust-lang/rust/pull/141295
### "RFC: Allow type inference for const or static" rfcs#3546
**Link:** https://github.com/rust-lang/rfcs/pull/3546
### "RFC: Unsafe Set Enum Discriminants" rfcs#3727
**Link:** https://github.com/rust-lang/rfcs/pull/3727
### "RFC: naming groups of configuration with `cfg_alias`" rfcs#3804
**Link:** https://github.com/rust-lang/rfcs/pull/3804
### "RFC: enable `derive(From)` for single-field structs" rfcs#3809
**Link:** https://github.com/rust-lang/rfcs/pull/3809
### "de-RFC: Remove unsized_locals" rfcs#3829
**Link:** https://github.com/rust-lang/rfcs/pull/3829
### "Tracking Issue for `const fn` `type_id`" rust#77125
**Link:** https://github.com/rust-lang/rust/issues/77125
### "Decide what we want about `macro_metavar_expr`" rust#137581
**Link:** https://github.com/rust-lang/rust/issues/137581
### "Original `pin!()` macro behavior cannot be expressed in Rust 2024" rust#138718
**Link:** https://github.com/rust-lang/rust/issues/138718
### "Allow while let chains on all editions" rust#140204
**Link:** https://github.com/rust-lang/rust/pull/140204
### "Lang proposal: Allow `#[cfg(...)]` within `asm!`" rust#140279
**Link:** https://github.com/rust-lang/rust/issues/140279
### "Add new `function_casts_as_integer` lint" rust#141470
**Link:** https://github.com/rust-lang/rust/pull/141470
### "Consider folkertdev's `c_variadic` proposal" rust#141524
**Link:** https://github.com/rust-lang/rust/issues/141524
### "Permit attributes on `use` items" rust#141704
**Link:** https://github.com/rust-lang/rust/issues/141704
### "Stabilize `#[cfg(version(...))]`, take 2" rust#141766
**Link:** https://github.com/rust-lang/rust/pull/141766
### "Should a `[..]` slice pattern constitute a discriminant read" rust#141825
**Link:** https://github.com/rust-lang/rust/issues/141825
### "`rustc_const_eval`: respect `target.min_global_align`" rust#142198
**Link:** https://github.com/rust-lang/rust/pull/142198
### "Decision: Use the condition name `rust_version` for RFC 2523" rust#142651
**Link:** https://github.com/rust-lang/rust/issues/142651
### "Stabilize `-Cmin-function-alignment`" rust#142824
**Link:** https://github.com/rust-lang/rust/pull/142824
### "Warn or error on duplicate attributes" rust#142836
**Link:** https://github.com/rust-lang/rust/issues/142836
### "A path towards erroring on nonsense attributes" rust#142838
**Link:** https://github.com/rust-lang/rust/issues/142838
### "const-eval can construct uninhabited values via recursive static initialization" rust#143047
**Link:** https://github.com/rust-lang/rust/issues/143047
### "Port the proc macro attributes to the new attribute parsing infrastructure" rust#143607
**Link:** https://github.com/rust-lang/rust/pull/143607
### "Nested panics and `std::thread::panicking`" rust#143612
**Link:** https://github.com/rust-lang/rust/issues/143612
### "Should_panic can be applied to non-tests" rust#143799
**Link:** https://github.com/rust-lang/rust/issues/143799
### "Port #[macro_export] to the new attribute parsing infrastructure" rust#143857
**Link:** https://github.com/rust-lang/rust/pull/143857
## Action item review
- [Action items list](https://hackmd.io/gstfhtXYTHa3Jv-P_2RK7A)
## Pending lang team project proposals
None.
## PRs on the lang-team repo
### "Frequently requested changes: add bypassing visibility" lang-team#323
**Link:** https://github.com/rust-lang/lang-team/pull/323
### "Add soqb`s design doc to variadics notes" lang-team#236
**Link:** https://github.com/rust-lang/lang-team/pull/236
### "Update auto traits design notes with recent discussion" lang-team#237
**Link:** https://github.com/rust-lang/lang-team/pull/237
### "Update hackmd link to a public link" lang-team#258
**Link:** https://github.com/rust-lang/lang-team/pull/258
### "Adding a link to "how to add a feature gate" in the experimenting how-to" lang-team#267
**Link:** https://github.com/rust-lang/lang-team/pull/267
### "text describing how other teams are enabled to make decisions." lang-team#290
**Link:** https://github.com/rust-lang/lang-team/pull/290
### "Fix link to agenda template" lang-team#315
**Link:** https://github.com/rust-lang/lang-team/pull/315
### "new decision process" lang-team#326
**Link:** https://github.com/rust-lang/lang-team/pull/326
### "Clarify that taking input in coroutines currently uses 'yield expressions'" lang-team#328
**Link:** https://github.com/rust-lang/lang-team/pull/328
### "Document experimental `P-lang-drag-[0-4]` and `I-lang-easy-decision`" lang-team#330
**Link:** https://github.com/rust-lang/lang-team/pull/330
## RFCs waiting to be merged
### "[RFC] Add `#[export_ordinal(n)]` attribute" rfcs#3641
**Link:** https://github.com/rust-lang/rfcs/pull/3641
### "Closing issues relevant to T-lang on this repo" rfcs#3756
**Link:** https://github.com/rust-lang/rfcs/issues/3756
## `S-waiting-on-team`
### "Fallback `{float}` to `f32` when `f32: From<{float}>` and add `impl From<f16> for f32`" rust#139087
**Link:** https://github.com/rust-lang/rust/pull/139087
### "Stabilize `fn_align`: `#[align(N)]` on functions" rust#140261
**Link:** https://github.com/rust-lang/rust/pull/140261
### "Mark all deprecation lints in name resolution as deny-by-default and report-in-deps" rust#143929
**Link:** https://github.com/rust-lang/rust/pull/143929
### "lexer: Treat more floats with empty exponent as valid tokens" rust#131656
**Link:** https://github.com/rust-lang/rust/pull/131656
### "`repr(tag = ...)` for type aliases" rfcs#3659
**Link:** https://github.com/rust-lang/rfcs/pull/3659
### "Remove unstable cfg `target(...)` compact feature" rust#130780
**Link:** https://github.com/rust-lang/rust/pull/130780
### "Add lint against (some) interior mutable consts" rust#132146
**Link:** https://github.com/rust-lang/rust/pull/132146
### "#[cold] on match arms" rust#120193
**Link:** https://github.com/rust-lang/rust/pull/120193
### "Permit duplicate imports" rust#141043
**Link:** https://github.com/rust-lang/rust/pull/141043
### "Stabilize `if let` guards (`feature(if_let_guard)`)" rust#141295
**Link:** https://github.com/rust-lang/rust/pull/141295
### "Permissions" rfcs#3380
**Link:** https://github.com/rust-lang/rfcs/pull/3380
### "Rename `AsyncIterator` back to `Stream`, introduce an AFIT-based `AsyncIterator` trait" rust#119550
**Link:** https://github.com/rust-lang/rust/pull/119550
### "Tracking Issue for `bare_link_kind`" rust#132061
**Link:** https://github.com/rust-lang/rust/issues/132061
### "Add compiler support for namespaced crates" rust#140271
**Link:** https://github.com/rust-lang/rust/pull/140271
### "Add new `function_casts_as_integer` lint" rust#141470
**Link:** https://github.com/rust-lang/rust/pull/141470
### "Stabilize `-Cmin-function-alignment`" rust#142824
**Link:** https://github.com/rust-lang/rust/pull/142824
### "Add debuginfo_transparent attribute for structs" rust#144223
**Link:** https://github.com/rust-lang/rust/pull/144223
## Proposed FCPs
**Check your boxes!**
### "Fallback `{float}` to `f32` when `f32: From<{float}>` and add `impl From<f16> for f32`" rust#139087
**Link:** https://github.com/rust-lang/rust/pull/139087
### "Arbitrary self types v2: stabilize" rust#135881
**Link:** https://github.com/rust-lang/rust/pull/135881
### "Stabilize return type notation (RFC 3654)" rust#138424
**Link:** https://github.com/rust-lang/rust/pull/138424
### "Mark all deprecation lints in name resolution as deny-by-default and report-in-deps" rust#143929
**Link:** https://github.com/rust-lang/rust/pull/143929
### "const-eval: full support for pointer fragments" rust#144081
**Link:** https://github.com/rust-lang/rust/pull/144081
### "Add lint against dangling pointers from local variables" rust#144322
**Link:** https://github.com/rust-lang/rust/pull/144322
### "`core::marker::NoCell` in bounds (previously known an `Freeze`)" rfcs#3633
**Link:** https://github.com/rust-lang/rfcs/pull/3633
### "Unsafe derives and attributes" rfcs#3715
**Link:** https://github.com/rust-lang/rfcs/pull/3715
### "RFC: Add an attribute for raising the alignment of various items" rfcs#3806
**Link:** https://github.com/rust-lang/rfcs/pull/3806
### "sanitizers: Stabilize AddressSanitizer and LeakSanitizer for the Tier 1 targets" rust#123617
**Link:** https://github.com/rust-lang/rust/pull/123617
### "RFC: No (opsem) Magic Boxes" rfcs#3712
**Link:** https://github.com/rust-lang/rfcs/pull/3712
### "Remove unstable cfg `target(...)` compact feature" rust#130780
**Link:** https://github.com/rust-lang/rust/pull/130780
### "Warn about C-style octal literals" rust#131309
**Link:** https://github.com/rust-lang/rust/pull/131309
### "Stabilize the `breakpoint` function" rust#142325
**Link:** https://github.com/rust-lang/rust/pull/142325
### "Unsafe fields" rfcs#3458
**Link:** https://github.com/rust-lang/rfcs/pull/3458
### "[RFC] externally implementable functions" rfcs#3632
**Link:** https://github.com/rust-lang/rfcs/pull/3632
### "Implement `PartialOrd` and `Ord` for `Discriminant`" rust#106418
**Link:** https://github.com/rust-lang/rust/pull/106418
### "Policy for lint expansions" rust#122759
**Link:** https://github.com/rust-lang/rust/issues/122759
### "Decide on path forward for attributes on expressions" rust#127436
**Link:** https://github.com/rust-lang/rust/issues/127436
### "Stabilize `if let` guards (`feature(if_let_guard)`)" rust#141295
**Link:** https://github.com/rust-lang/rust/pull/141295
### "RFC: Allow type inference for const or static" rfcs#3546
**Link:** https://github.com/rust-lang/rfcs/pull/3546
### "Allow `&&`, `||`, and `!` in `cfg`" rfcs#3796
**Link:** https://github.com/rust-lang/rfcs/pull/3796
### "de-RFC: Remove unsized_locals" rfcs#3829
**Link:** https://github.com/rust-lang/rfcs/pull/3829
### "Stabilize associated type position impl Trait (ATPIT)" rust#120700
**Link:** https://github.com/rust-lang/rust/pull/120700
### "Allow while let chains on all editions" rust#140204
**Link:** https://github.com/rust-lang/rust/pull/140204
### "Stabilize `#[cfg(version(...))]`, take 2" rust#141766
**Link:** https://github.com/rust-lang/rust/pull/141766
### "Decision: Use the condition name `rust_version` for RFC 2523" rust#142651
**Link:** https://github.com/rust-lang/rust/issues/142651
### "new decision process" lang-team#326
**Link:** https://github.com/rust-lang/lang-team/pull/326
## Active FCPs
### "RFC: enable `derive(From)` for single-field structs" rfcs#3809
**Link:** https://github.com/rust-lang/rfcs/pull/3809
### "Port the proc macro attributes to the new attribute parsing infrastructure" rust#143607
**Link:** https://github.com/rust-lang/rust/pull/143607
### "Port #[macro_export] to the new attribute parsing infrastructure" rust#143857
**Link:** https://github.com/rust-lang/rust/pull/143857
## P-critical issues
None.
Sign in with Wallet
Connect another wallet