The Rust RFC process does not seem as amazing as I initially thought

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • rfcs

    RFCs for changes to Rust

  • This seems like a particularly egregious example Delegation. This seems so important because everywhere everyone seems to beat it over your head of how Rust prefers composition over inheritance and how amazing that is. But as a newcomer it seems like the language does not make it easy to do composition. Without proper delegation you have to manually write implementations for newtype methods and traits, when a delegation syntax would be extremely helpful to remove the boilerplate especially when you have so many methods. It seems like a tremendous effort has been put into this RFC and seems to be reasonably popular.

  • rust-delegate

    Rust method delegation with less boilerplate

  • Macros, probably. For example this one, that was already made by someone else, published on crates.io and is actively maintained. If the feature is already possible in rust, but requires a lot of boilerplate, then macros are the answer 99% of the time.

  • 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.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts