rust-lang logo


RFCs for changes to Rust (by rust-lang)


Basic rfcs repo stats
7 days ago

rust-lang/rfcs is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

Rfcs Alternatives

Similar projects and alternatives to rfcs
  • GitHub repo rust

    Empowering everyone to build reliable and efficient software.

  • GitHub repo tokio

    A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

  • GitHub repo rust-analyzer

    A Rust compiler front-end for IDEs

  • GitHub repo unsafe-code-guidelines

    Home for the Unsafe Code Guidelines working group.

  • GitHub repo rfcs

    RFCs for changes to Rust (by scottmcm)

  • GitHub repo Cargo

    The Rust package manager

  • GitHub repo

    Source code for

  • GitHub repo Rocket

    A web framework for Rust.

  • GitHub repo futures-rs

    Zero-cost asynchronous programming in Rust

  • GitHub repo rustfmt

    Format Rust code

  • GitHub repo case-studies

    Analysis of various tricky Rust code

  • GitHub repo rust-audit

    Make production Rust binaries auditable

  • GitHub repo dynstack

    A stack for rust trait objects that minimizes allocations

  • GitHub repo syscalls-rs

  • GitHub repo simd-adler32

  • GitHub repo tail

    My implementation of the tail tool to (continuously) read the tail end of a file. See (by LeCyberDucky)

  • GitHub repo Rustlings

    :crab: Small exercises to get you used to reading and writing Rust code!

  • GitHub repo json

    Strongly typed JSON library for Rust (by serde-rs)

  • GitHub repo heroku-buildpack-rust

    A buildpack for Rust applications on Heroku, with full support for Rustup, cargo and build caching.

  • GitHub repo serde-yaml

    Strongly typed YAML library for Rust

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better rfcs alternative or higher similarity.


Posts where rfcs has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-04-12.
  • Defining how to destructure objects, without boilerplate code
    Well, you can fix that if you encode partial moves in the type system / the function signature. Similar to the idea of partial borrowing (an RCF “suggestion”) in Rust.
  • Lifetimes issue | 2021-04-12
    GATs (generic associated types) will make this pattern possible, like so:
  • Hey Rustaceans! Got an easy question? Ask here (15/2021)! | 2021-04-12
  • Why rustc's clamp is superior when compared to its Clang "equivalent" | 2021-04-10
    Kudos to those who participated in the RFC discussion about this to ensure it was possible:
  • A look at LLVM: comparing clamp implementations | 2021-04-09
    Rust's RFC for clamp has specifically tuned the definition and handling of NaN to be able to generate good assembly. I'm glad people have noticed and appreciate this.

  • simd-adler32: Computing Adler-32 checksums at ~40GiB/s using AVX2 | 2021-04-09
    Yes, but only on x86 (e.g. see the cpuid-bool crate). On other targets we will need something like RFC 2725.
  • Major Change Proposal: Update the existing musl targets to be dynamically linked | 2021-04-08
    Certainly there is quite a lot of emphasis put on their stability... a distinction is maintained between stable and unstable flags to rustc and cargo for instance. Unstable flags are hidden on stable versions of the compilers. There's an explicit stabilization process (at least for cargo?) similar to that of language features. Backwards incompatible changes to things like the feature resolver have been implemented in backwards compatible ways. Stabilization of things like the panic flag feature prominently in rfcs suggesting that stabilization is considered a very significant change. | 2021-04-08
  • This Week in Rust 385 | 2021-04-08
    This weeks "RFC that will effect you": | 2021-04-08
    Yes! Very happy with! This saves me from going full proc macro when doing tuple indexing in a decl macro
  • Help creating an executable | 2021-04-08
    you need to set windows_subsystem(windows) for that to work.
  • Is it OK to transmute `Vec<X>` into `Vec<(X, ())>`? | 2021-04-07
    IIRC there are some subtle implications in moving the Vec into mem::forget’s argument depending on the exact model being used to define the rules of Undefined Behavior (which is not completely decided for Rust so far). may have some discussion.
  • The modern packager’s security nightmare | 2021-04-06
    This can be solved by embedding a list of linked libraries and their versions in every binary by default. You can find the RFC here, and I've also made a working implementation of this as a crate:
  • Sending tuples from Node to Rust and back | 2021-04-05
    The RFC discussion also includes an example of how to count repetitions of an input fragment in current Rust:
  • Grids in Rust, part 2: const generics | 2021-04-03
    I am a bit under-educated about the exact specifics here, but I should note that this feature was originally literally dependent types.



    * (the design that was accepted, in the end)

    (I am not actually 100% sure if rfc 2000 meets the by-the-book definition of "dependent types", my copy of Pierce has been collecting dust. Really gotta study up more on this stuff.)