api-guidelines
Rust API guidelines (by rust-lang)
patterns
A catalogue of Rust design patterns, anti-patterns and idioms (by rust-unofficial)
api-guidelines | patterns | |
---|---|---|
32 | 63 | |
1,203 | 7,722 | |
0.6% | 1.4% | |
3.3 | 7.5 | |
about 2 months ago | 11 days ago | |
Handlebars | ||
Apache License 2.0 | Mozilla Public License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
api-guidelines
Posts with mentions or reviews of api-guidelines.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-11.
- Best practices for designing traits in public crates?
-
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
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
The API guidelines will help you write nice APIs. Clippy will usually at least find some things, try running with -Wclippy::pedantic for a lot more messages. Also you can ask mentors for specific guidance. Hope that helps.
-
Naming traits
There has been some previous discussion on this here: https://github.com/rust-lang/api-guidelines/discussions/28
-
What is the proper guidance on using generics as parameters for an API
I'm currently writing an API and using the API guidelines book. On the Flexibility page, there's a section on using generics as function parameters to minimize assumptions. The issue that I'm having is that the only example it gives is std::fs::File::open. Specifically, I want to know what is the "standard" way to use generics as parameters?
-
Prefixes in name and Reexports
I search up in the rust-api-guideline, but no luck finding something like this. There used to be an Organization according to this thread, but upon digging the repo commits, it was deleted by this commit. "We can reintroduce this section if we come up with a way to give firmer advice here."
-
What are some good practices when writing rust?
public api of a library should follow Rust API Guidelines.
-
astro-float 0.6.6 arbitrary precision floating point library update
API was made compliant with Rust API Guidelines.
-
Picking Up Rust Before C With My Goals In Mind?
Finally, there's also the Little Book of Rust Books where you could look for tutorial materials or things like like Rust Design Patterns, Rust API Guidelines, and The Rust Performance Book. (See also rust-learning)
-
Learning rust
Rust API Guidelines: If you're planning on building libraries or APIs in Rust, these guidelines provide recommendations for designing and presenting APIs in the language. They're written by the Rust library team, based on their experience building the Rust standard library and other crates in the ecosystem.
patterns
Posts with mentions or reviews of patterns.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-11.
- 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?
When comparing api-guidelines and patterns you can also consider the following projects:
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
rust-typed-builder - Compile-time type-checked builder derive
idiomatic-rust - 🦀 A peer-reviewed collection of articles/talks/repos which teach concise, idiomatic Rust.
rust - Empowering everyone to build reliable and efficient software.
book - The Rust Programming Language
gdnative - Rust bindings for Godot 3
Godot - Godot Engine – Multi-platform 2D and 3D game engine
vulkano - Safe and rich Rust wrapper around the Vulkan API
api-guidelines vs wasm-bindgen
patterns vs nomicon
api-guidelines vs too-many-lists
patterns vs rust-typed-builder
api-guidelines vs idiomatic-rust
patterns vs too-many-lists
api-guidelines vs rust
patterns vs book
api-guidelines vs gdnative
patterns vs idiomatic-rust
api-guidelines vs Godot
patterns vs vulkano