rfcs
rfcs copied to clipboard
rust-lang
RFCs for changes to Rust
Add a helper for primitive pointer types to facilitate modifying the address of a pointer. This mechanism is intended to enable the use of architecture features such as AArch64 Top-Byte...
[#67792]: https://github.com/rust-lang/rust/issues/67792 [RFC #3628]: https://github.com/rust-lang/rfcs/pull/3628 [RFC #3668]: https://github.com/rust-lang/rfcs/pull/3668 [RFC #243]: https://github.com/rust-lang/rfcs/pull/243 [RFC #2071]: https://github.com/rust-lang/rfcs/blob/master/text/2071-impl-trait-existential-types.md [asyncfg]: https://rust-lang.github.io/rust-project-goals/2024h2/async.html [droporder]: https://github.com/rust-lang/rust/blob/0b16baa570d26224612ea27f76d68e4c6ca135cc/compiler/rustc_ast_lowering/src/item.rs#L1179-L1210 [WCIF]: https://journal.stuffwithstuff.com/2015/02/01/what-flavor-is-your-function/ # Summary [summary]: #summary This RFC unblock the stabilization of...
## Summary Relax the requirements on struct field ordering for dynamically sized fields for `repr(Rust)` and `repr(transparent)`, such that `?Sized` fields can be anywhere in the field list, as long...
Many crates support deriving their traits with `derive(Trait)`. Today, this requires defining proc macros, in a separate crate, typically with several additional dependencies adding substantial compilation time, and typically guarded...
This RFC proposes `Result::todo` and `Option::todo` functions which work like `.unwrap()` but imply that error handling should be implemented later. As an example: ```rs // unwrap is still used for...
## Summary Currently, the operational semantics of the type [`alloc::boxed::Box`](https://doc.rust-lang.org/beta/alloc/boxed/struct.Box.html) is in dispute, but the compiler adds llvm `noalias` to it. To support it, the current operational semantics models have...
This RFC outlines the case for promoting the Rust riscv64gc-unknown-linux-gnu target to Tier-1 (without host tools) status. Shout out to @hoverbear, @danielsilverstone-ct for their support. [Rendered](https://github.com/robin-randhawa-sifive/rust-lang-rfcs/blob/promote-riscv64-unknown-linux-gnu-to-tier1-without-host-tools/text/0000-promote-riscv64gc-unknown-linux-gnu-to-tier1-without-host-tools.md)
Related to https://github.com/rust-lang/rfcs/issues/2902 and https://internals.rust-lang.org/t/pre-rfc-add-compile-warning-macro/9370, I want a compile_warning! macro that is similar to compile_error! except that it is not a hard error. Here is a motivating use case. Say...
Although I know this idea will get downvoted, I still wanted to share my thoughts. After exploring some crates, I don’t feel that using `GC` provides a seamless experience for...
## Summary Adds the builtin types `u` and `i`, allowing integers with an arbitrary size in bits. [Rendered](https://github.com/clarfonthey/rust-rfcs/blob/generic-integers-v2/text/0000-generic-integers.md) ## Details This is a follow-up to #2581, which was previously postponed....