Stats
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
-
-
tokio
A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
-
Scout APM
Scout APM - Leading-edge performance monitoring starting at $39/month. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
-
-
-
-
-
-
-
-
-
-
tail
My implementation of the tail tool to (continuously) read the tail end of a file. See https://en.wikipedia.org/wiki/Tail_(Unix) (by LeCyberDucky)
-
-
-
heroku-buildpack-rust
A buildpack for Rust applications on Heroku, with full support for Rustup, cargo and build caching.
-
Posts
-
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
GATs (generic associated types) will make this pattern possible, like so:
- Hey Rustaceans! Got an easy question? Ask here (15/2021)!
-
Why rustc's clamp is superior when compared to its Clang "equivalent"
Kudos to those who participated in the RFC discussion about this to ensure it was possible: https://github.com/rust-lang/rfcs/pull/1961#issuecomment-289723144
-
A look at LLVM: comparing clamp implementations
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
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
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.
Sure! https://github.com/rust-lang/rfcs/pull/2803
-
This Week in Rust 385
This weeks "RFC that will effect you": https://github.com/rust-lang/rfcs/pull/3058
Yes! Very happy with https://github.com/rust-lang/rfcs/pull/3086! This saves me from going full proc macro when doing tuple indexing in a decl macro
-
Help creating an executable
you need to set windows_subsystem(windows) for that to work. https://github.com/rust-lang/rfcs/blob/master/text/1665-windows-subsystem.md
-
Is it OK to transmute `Vec<X>` into `Vec<(X, ())>`?
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). https://github.com/rust-lang/rfcs/pull/2756 may have some discussion.
-
The modern packager’s security nightmare
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: https://github.com/Shnatsel/rust-audit
-
Sending tuples from Node to Rust and back
The RFC discussion also includes an example of how to count repetitions of an input fragment in current Rust: https://github.com/rust-lang/rfcs/pull/3086#issuecomment-783554746
-
Grids in Rust, part 2: const generics
I am a bit under-educated about the exact specifics here, but I should note that this feature was originally literally dependent types.
* https://github.com/rust-lang/rfcs/pull/1657
* https://github.com/rust-lang/rfcs/issues/1930
* https://github.com/rust-lang/rfcs/pull/2000 (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.)