rfcs
rfcs copied to clipboard
RFCs for changes to Rust
This RFC guarantees the representation of `&str` and `&[T]` to be equivalent to a `repr(C)` struct containing a pointer and a length. [Rendered](https://github.com/cramertj/rfcs/blob/slice-repr/text/0000-guaranteed-slice-repr.md)
This RFC proposes adding ergonomic `input!`, `inputln!` and may `try_input!` macros to Rust for reading user input, inspired by Python’s `input()`. These macros simplify input handling, improve beginner experience, and...
[Rendered](https://github.com/PixelDust22/rfcs/blob/layout-packed-aligned/text/0000-layout-packed-aligned.md) This issue was introduced in the [original implementation](https://github.com/rust-lang/rust/issues/33158) of `#[repr(packed(N))]` and have since underwent extensive community discussions: - [#[repr(align(N))] fields not allowed in #[repr(packed(M>=N))] structs](https://github.com/rust-lang/rust/issues/100743) - [repr(C) does not...
See discussion on internals [here](https://internals.rust-lang.org/t/pre-rfc-allow-procedural-macros-to-be-placed-in-the-same-crate-package-as-app/23005). I feel the need to clarify that this is not about crates, but packages. I had them confused the initial time I wrote the document....
When writing proc macro, sometimes it's convenient to parse external data file and generate code accordingly. It would be nice to allow creating `Span`s corresponding to byte ranges within the...
This proposal was initially shared in a [Reddit post](https://www.reddit.com/r/rust/comments/1kwud96/proposal_to_reconcile_generics_and_rusts_orphan/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) I authored to introduce the idea and gather community feedback: “Proposal to reconcile generics and Rust’s orphan rule” While the post...
Please remember to create inline comments for discussions to keep this RFC manageable and discussion trees resolveable. [Rendered](https://github.com/oli-obk/rfcs/blob/const-trait-impl/text/0000-const-trait-impls.md) Related: - https://github.com/rust-lang/rust/issues/67792
[Rendered](https://github.com/lolbinarycat/rust-rfcs/blob/doc-consts/text/0000-doc-consts.md)
My understanding is that T-lang is not interested in following discussion on the RFCs repo that is not actual RFC. Various proposals seem interesting but are unfortunately in the form...
This adds an RFC proposing a new attribute that would help detect mistakes when a parameter of a function is not used after the function returns. E.g. when inserting into...