eventually-rs
patterns
eventually-rs | patterns | |
---|---|---|
3 | 63 | |
539 | 7,722 | |
0.7% | 1.4% | |
6.3 | 7.5 | |
19 days ago | 14 days ago | |
Rust | Handlebars | |
MIT License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
eventually-rs
-
Best practices for designing traits in public crates?
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.
-
eventually-go: Idiomatic Event Sourcing for Go
But you can read it in the Rust version README! :D
patterns
- Best practices for designing traits in public crates?
-
Ask HN: Learning new coding patterns – how to start?
For OOP design patterns in Rust, see: https://rust-unofficial.github.io/patterns/
For a book on FP, see: https://www.manning.com/books/grokking-simplicity
- Haskell mini-patterns handbook (2020)
- Is there any site with Dos and Don'ts in Rust?
-
Functional Options Pattern in Go and Rust
Just wanting to let this here for some further input: - https://rust-lang.github.io/api-guidelines/ - https://rust-unofficial.github.io/patterns/ - https://deterministic.space/elegant-apis-in-rust.html
-
Rust exercices for tech interview
Rust Design Patterns
-
I want some help learning design patterns
I know about Rust Design Pattern what are your reviews for the same?
-
I've been writing C# for nearly a decade, but I want to learn how to build programs with Rust. What do I need to change about how I structure my code?
Once you've finished with The Book and possibly Programming Rust, 2nd Edition if you've got the cash for a paid book, read Learning Rust With Entirely Too Many Linked Lists (it helps to solidify what ownership and borrowing mean for data structures) and Rust Design Patterns.
-
Is there a coding style and set of best-practices that avoid (not bypass) "fighting the borrow checker"?
Well, there's https://rust-unofficial.github.io/patterns/ for a start.
-
Comprehensive Rust 🦀 is now available in Korean!
Love the translation pipeline, currently looking into adopting that as well for the Rust patterns book!
What are some alternatives?
thalo - An Event Sourcing runtime with WebAssembly & embedded event store
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
eventsourcing - Event Sourcing in Go
rust-typed-builder - Compile-time type-checked builder derive
simd-json - Rust port of simdjson
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
rsfbclient - Rust Firebird Client
book - The Rust Programming Language
saving-goals-go - Example Event-Sourced microservice using https://github.com/eventually-rs/eventually-go [Moved to: https://github.com/get-eventually/saving-goals-go]
idiomatic-rust - 🦀 A peer-reviewed collection of articles/talks/repos which teach concise, idiomatic Rust.
eventually-go - Idiomatic Domain-driven Design, CQRS and Event Sourcing for Go
vulkano - Safe and rich Rust wrapper around the Vulkan API