api-guidelines
idiomatic-rust
api-guidelines | idiomatic-rust | |
---|---|---|
32 | 4 | |
1,203 | 5,927 | |
0.6% | - | |
3.3 | 7.0 | |
about 2 months ago | 10 days ago | |
Rust | ||
Apache 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.
api-guidelines
- 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.
idiomatic-rust
-
Ask HN: What are some good rust code to read to learn the language?
Here is a peer-reviewed collection - https://github.com/mre/idiomatic-rust
-
Resources for Rust best practices?
There is a list on GitHub that has good resources: https://github.com/mre/idiomatic-rust
-
Where can I learn advanced Rust and how to think in Rust idioms?
You need this - https://github.com/mre/idiomatic-rust
- Is there a Rust equivalent to the C++ Standard?
What are some alternatives?
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
patterns - A catalogue of Rust design patterns, anti-patterns and idioms
toydb - Distributed SQL database in Rust, written as a learning project
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
rust - Empowering everyone to build reliable and efficient software.
lust - A parser, compiler, and virtual machine evaluator for a minimal subset of Lua; written from scratch in Rust.
gdnative - Rust bindings for Godot 3
extreme - extremely boring async function runner!
Godot - Godot Engine – Multi-platform 2D and 3D game engine
noria - Fast web applications through dynamic, partially-stateful dataflow