Rust 2024 survey about lang-team

[tgross35]

I did find some discussion about this rust-lang/rfcs#2848. It seems like the kind of thing where somebody just needs to start writing an RFC and see how well it sticks.

@bstrie if you want to throw some loose ideas into a HackMD document, I don't mind helping formulate them into an RFC (I'm sure others would join too)

[Jules-Bertholet]

rust-lang/rust#59878 would be nice to fix, if negative impls can be stabilized on time

[Jules-Bertholet]

Some more open RFCs that are potentially edition-sensitive:

• rust-lang/rfcs#2484 (deprecate as?)
• rust-lang/rfcs#2937 (deprecate static mut?)
• rust-lang/rfcs#3240
• rust-lang/rfcs#3319 (future possibility: ?Sized → ?Aligned)
• rust-lang/rfcs#3373
• rust-lang/rfcs#3396
• rust-lang/rfcs#3410 (future possibility)

Open issues not previously mentioned:

• Much of https://github.com/rust-lang/rust/labels/A-edition-2018-lints
• Much of https://github.com/rust-lang/rust/labels/C-future-compatibility
• rust-lang/rust#35121 (inference fallback)
• rust-lang/rust#43781 (doc_auto_cfg)
• rust-lang/rust#49441
• rust-lang/rust#67264
• rust-lang/rust#71668
• rust-lang/rust#80619
• rust-lang/rust#89151 (RFC future possibility)
• rust-lang/rust#94978
• rust-lang/rust#95228 (deprecate pointer-integer as casts?)
• rust-lang/rust#98862
• rust-lang/rust#99195 and rust-lang/rust#108069 (make overflowing_literals deny or a hard error?)
• rust-lang/rust#100706

[joshtriplett]

Some potentially useful links:

• https://blog.rust-lang.org/inside-rust/2022/04/04/lang-roadmap-2024.html
• https://github.com/rust-lang/rust/labels/A-edition-2024
• https://github.com/rust-lang/rust/labels/lang-team-202x-edition

[nikomatsakis]

Scheduled for 2023-06-28 and placeholder doc created

[Lokathor]

the unsafe extern blocks RFC would be edition sensitive, rust-lang/rfcs#3439

[RalfJung]

rust-lang/rfcs#3325 is intended to be edition sensitive.

Not sure if there is any point in giving another shot at "removing long-deprecated items that are unsound or almost impossible to use soundly" (mem::uninitialized, before_exec).

[tgross35]

I know there was some discussion about changing the Range/Iter/IntoIterator/Copy fiasco at some point, but I don't believe a concrete proposal came out of it, or if it is even "fixable"

[bstrie]

@tgross35 I think the Range situation is improvable, although naturally having an RFC is a prerequisite and nobody's going to hold up the edition if an RFC doesn't materialize. I have some thoughts in that area that might lead to an RFC, although I need to page the discussion back into my head.

[Jules-Bertholet]

https://github.com/rust-lang/rust/labels/WG-epoch also merits review

[fmease]

I know this issue is not the right place (the meeting has already happened as far as I can tell) but since there isn't a proper Zulip stream yet (ah, there is one), I'm just gonna nominate the (breaking) feature lazy_type_alias here for inclusion into Rust 2024. It still needs some polish though.

This directly addresses the following point found at the bottom of the HackMD doc:

other things that came up after the meeting

• Remove where clauses on type aliases or make them work.

Edit: I'm gonna open a Zulip topic for this later, too. Edit: Zulip topic.

[tgross35]

@bstrie I don't know whether you had time to put anything together, but I started a rough outline https://hackmd.io/@8W5l8q6-Qyyn_vKh2-L0RQ/SJ0sBpb22. It should be open for editing if anyone wants to contribute (discussion should probably happen in comments in the doc so as to not derail this thread).