Best practices for designing traits in public crates?

1. eventually-rs

   1 3 561 5.5 Rust

   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.

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. patterns

   2 65 8,307 6.5 Handlebars

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

   

4. api-guidelines

   3 32 1,255 3.3

   Rust API guidelines (by rust-lang)

   

Suggest a related project