Best practices for designing traits in public crates?

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
  • eventually-rs

    Event Sourcing for Rust

  • While I like now that there is a single trait involved (which also makes it easier to write super-types), I don't like the requirement for those associated type names like type GetError and type SaveError. I also don't particularly like the idea of hiding everything behind a single Error type, as it kinda defeats the purpose of having such a nice type system like the one Rust has.

  • patterns

    A catalogue of Rust design patterns, anti-patterns and idioms

  • 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
  • api-guidelines

    Rust API guidelines (by rust-lang)

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