SaaSHub helps you find the best software and product alternatives Learn more →
Rfcs Alternatives
Similar projects and alternatives to rfcs
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
rfcs reviews and mentions
-
A four year plan for async Rust
As the person who proposed this feature - among lots of other ones for async Rust, like run-to-completion async functions (https://github.com/Matthias247/rfcs/blob/e7fd7042f8069e9126e...), structured concurrency, cancellation tokens, etc) - I can unfortunately share this sentiment. It seemed really hard to land anything in async Rust since the priorities don't seem overly clear. Therefore I put a pause on all contribution attempts and went back to just using Rust as a user.
-
Changing the Rules of Rust
I assume you mean "spawned futures" - because regular Futures obviously don't have to be 'static. You can run as many of them as you want on a single task by using Future combinators like join/select.
If this is mostly about scoped async task and the ability to reference data from the parent task, then there also had been a different proposal being discussed which provides the same guarantee: A new Future type (e.g. CompletionFuture), which by represents an async function that needs to be driven to completion. See https://github.com/Matthias247/rfcs/pull/1 for details. However since this propsal is already 3 years old and hasn't gotten and interest by the Rust async WG, it's probably also not going forward.
-
Async Cancellation
>Matthias247 has done work to flesh out what this looks like: https://github.com/Matthias247/rfcs/pull/1
By making a new kind of async function that cannot be called from existing async functions, I see. I started reading it with the expectation that RTCFutures would automatically spawn() themselves to enforce the RTC requirement. I'm pessimistic this approach will catch on, but let's see how it goes.
-
A note from our sponsor - SaaSHub
www.saashub.com | 8 Jun 2024
Stats
Matthias247/rfcs is an open source project licensed under Apache License 2.0 which is an OSI approved license.